 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| rabbitcore rcm3365/RCM3375 c-programmable core module with nand flash mass storage and ethernet user?s manual 019?0150 ? 080528?g
rabbitcore rcm3365/RCM3375 rabbit semiconductor inc. www.rabbit.com rabbitcore rcm3365/RCM3375 user?s manual part number 019-0150 ? 080528?g ? printed in u.s.a. ?2005?2008 digi international inc. ? all rights reserved. digi international reserves the right to make changes and improvements to its products without providing notice. trademarks rabbit, rabbitcore, and dynamic c are register ed trademarks of di gi international inc. rabbit 3000 is a trademark of digi international inc. xd-picture card is a trademark of fuji photo film co., olympus corporation, and toshiba corporation. no part of the contents of this manual may be reproduced or transmitted in any form or by any means without the express written permission of digi international. permission is granted to make one or more copies as long as the copyright page contained therein is included. these copies of the manuals may not be let or sold for any reason without the express written permission of digi international. the latest revision of this manual is available on the rabbit web site, www.rabbit.com , for free, unregistered download. user?s manual t able of c ontents chapter 1. introduction 1 1.1 rcm3365 and RCM3375 features .............................................................................................. ........2 1.2 comparing the rcm3900/rcm3910 and rcm3365/RCM3375 ........................................................4 1.3 advantages of the rcm3365 and RCM3375..................................................................................... ..5 1.4 development and evaluation tools.......................................................................................... ............6 1.4.1 rcm3365/RCM3375 development kit .......................................................................................6 1.4.2 software ................................................................................................................ ........................7 1.4.3 accessories............................................................................................................. .......................7 1.4.4 online documentation .................................................................................................... ..............7 chapter 2. getting started 9 2.1 install dynamic c ......................................................................................................... ........................9 2.2 hardware connections...................................................................................................... ..................10 2.2.1 step 1 ? attach module to prototyping board..........................................................................10 2.2.2 step 2 ? connect serial programmi ng cable............................................................................11 2.2.2.1 programming via ethernet option ..................................................................................... 1 2 2.2.3 step 3 ? connect power .................................................................................................. ..........13 2.2.3.1 alternate power-supply connec tions ................................................................................ 13 2.3 starting dynamic c ........................................................................................................ ....................14 2.3.1 running dynamic c vi a serial programming cable ..................................................................15 2.3.1.1 run a sample program.................................................................................................. ..... 15 2.3.1.2 troubleshooting ....................................................................................................... .......... 15 2.3.2 running dynamic c via ethernet cables ................................................................................... 16 2.3.2.1 run a sample program.................................................................................................. ..... 16 2.3.2.2 troubleshooting ....................................................................................................... .......... 17 2.4 where do i go from here? .................................................................................................. .............17 2.4.1 technical support ....................................................................................................... ................17 chapter 3. running sample programs 19 3.1 introduction.............................................................................................................. ...........................19 3.2 sample programs ........................................................................................................... .....................20 3.2.1 use of nand flash....................................................................................................... .............21 3.2.2 hot-swapping xd-picture card ............................................................................................ ......23 3.2.3 serial communication.................................................................................................... .............24 3.2.4 real-time clock ......................................................................................................... ................25 3.2.5 rabbitnet ............................................................................................................... .....................26 3.2.6 other sample programs ................................................................................................... ...........26 chapter 4. hardware reference 27 4.1 rcm3365/RCM3375 inputs and outputs ........................................................................................ ..28 4.1.1 memory i/o interface .................................................................................................... .............33 4.1.2 other inputs and outputs ................................................................................................ ............33 4.1.3 leds .................................................................................................................... .......................33 4.2 serial communication ...................................................................................................... ..................34 4.2.1 serial ports ............................................................................................................ ......................34 4.2.2 ethernet port ........................................................................................................... ....................34 4.2.3 serial programming port................................................................................................. ............35 rabbitcore rcm3365/RCM3375 4.3 serial programming cable .................................................................................................. ............... 36 4.3.1 changing between program mode and run mode.................................................................... 36 4.3.2 standalone operation of the rcm3365/RCM3375 ................................................................... 37 4.4 memory .................................................................................................................... .......................... 38 4.4.1 sram.................................................................................................................... ..................... 38 4.4.2 flash eprom............................................................................................................. ................ 38 4.4.3 nand flash.............................................................................................................. ................. 38 4.5 other hardware ............................................................................................................ ...................... 40 4.5.1 clock doubler ........................................................................................................... ................. 40 4.5.2 spectrum spreader....................................................................................................... ............... 40 chapter 5. software reference 41 5.1 more about dynamic c ...................................................................................................... ............... 41 5.1.1 developing programs remotely with dynamic c ..................................................................... 43 5.2 dynamic c functions...................................................................................................... .................. 44 5.2.1 digital i/o............................................................................................................. ...................... 44 5.2.2 sram use................................................................................................................ .................. 44 5.2.3 serial communication drivers ............................................................................................ ....... 45 5.2.4 tcp/ip drivers .......................................................................................................... ................. 45 5.2.5 nand flash drivers...................................................................................................... ............ 45 5.2.6 prototyping board functions............................................................................................. ......... 46 5.2.6.1 board initialization .................................................................................................. .......... 46 5.2.6.2 digital i/o........................................................................................................... ............... 47 5.2.6.3 switches, leds, and relay ............................................................................................. .. 48 5.2.6.4 serial communication .................................................................................................. ..... 49 5.2.6.5 rabbitnet port ........................................................................................................ ........... 50 5.3 upgrading dynamic c ....................................................................................................... ................ 52 5.3.1 extras.................................................................................................................. ........................ 52 chapter 6. using the tcp/ip features 53 6.1 tcp/ip connections ........................................................................................................ ................... 53 6.2 tcp/ip primer on ip addresses ............................................................................................. ............ 55 6.2.1 ip addresses explained.................................................................................................. ............ 57 6.2.2 how ip addresses are used ............................................................................................... ........ 58 6.2.3 dynamically assigned internet addresses................................................................................. 59 6.3 placing your device on the network ........................................................................................ ........ 60 6.4 running tcp/ip sample programs............................................................................................ ........ 61 6.4.1 how to set ip addresses in the sample programs..................................................................... 62 6.4.2 how to set up your computer for direct connect.................................................................... 63 6.5 run the pingme.c sample program........................................................................................... ..... 64 6.6 running additional sample programs with direct connect ............................................................ 64 6.6.1 rabbitweb sample programs............................................................................................... ...... 65 6.7 where do i go from here? .................................................................................................. ............. 65 appendix a. rcm3365/RCM3375 specifications 67 a.1 electrical and mechanical characteristics ................................................................................. ....... 68 a.1.1 headers ................................................................................................................. ..................... 72 a.2 bus loading ............................................................................................................... ....................... 73 a.3 rabbit 3000 dc characteristics ............................................................................................ ............ 76 a.4 i/o buffer sourcing and sinking limit..................................................................................... ........ 77 a.5 jumper configurations ..................................................................................................... ................. 78 a.6 conformal coating ......................................................................................................... ................... 80 appendix b. prototyping board 81 b.1 introduction .............................................................................................................. ......................... 82 b.1.1 prototyping board features .............................................................................................. ......... 83 b.2 mechanical dimensions and layout .......................................................................................... ....... 85 user?s manual b.3 power supply .............................................................................................................. .......................87 b.4 using the prototyping board............................................................................................... ...............88 b.4.1 adding other components................................................................................................. ........89 b.4.2 digital i/o............................................................................................................. ......................90 b.4.2.1 digital inputs ........................................................................................................ ............. 90 b.4.3 cmos digital outputs .................................................................................................... ...........91 b.4.4 sinking digital outputs................................................................................................. .............91 b.4.5 relay outputs ........................................................................................................... ..................91 b.4.6 serial communication.................................................................................................... ............92 b.4.6.1 rs-232 ................................................................................................................ ............... 93 b.4.6.2 rs-485 ................................................................................................................ ............... 94 b.4.7 rabbitnet ports ......................................................................................................... .................95 b.4.8 other prototyping board modules ......................................................................................... ....96 b.4.9 quadrature decoder ...................................................................................................... .............96 b.4.10 stepper-motor control .................................................................................................. ...........96 b.5 prototyping board jumper configurations ................................................................................... .....98 b.6 use of rabbit 3000 parallel ports ......................................................................................... ...........100 appendix c. lcd/keypad module 103 c.1 specifications ............................................................................................................ .......................103 c.2 contrast adjustments for all boards ....................................................................................... ........105 c.3 keypad labeling ........................................................................................................... ...................106 c.4 header pinouts ............................................................................................................ .....................107 c.4.1 i/o address assignments................................................................................................. ........107 c.5 mounting lcd/keypad module on the prototyping board ............................................................108 c.6 bezel-mount installation.................................................................................................. ................109 c.6.1 connect the lcd/keypad module to your prototyping board...............................................111 c.7 sample programs ........................................................................................................... ..................112 c.8 lcd/keypad module function calls .......................................................................................... ....113 c.8.1 lcd/keypad module initialization........................................................................................ ..113 c.8.2 leds.................................................................................................................... .....................113 c.8.3 lcd display............................................................................................................. ................114 c.8.4 keypad.................................................................................................................. ....................130 appendix d. power supply 133 d.1 power supplies............................................................................................................ .....................133 d.1.1 battery backup.......................................................................................................... ...............133 d.1.2 battery-backup circuit .................................................................................................. ..........134 d.1.3 reset generator......................................................................................................... ...............135 appendix e. programming via ethernet crossover cable 137 e.1 load tcp/ip parameters to the rcm3365 module.........................................................................138 e.2 load tcp/ip parameters to the pc, notebook, or workstation ......................................................139 e.3 run a program............................................................................................................. .....................141 e.3.1 troubleshooting......................................................................................................... ...............141 appendix f. rabbitnet 143 f.1 general rabbitnet description ............................................................................................. ...........143 f.1.1 rabbitnet connections ................................................................................................... ..........143 f.1.2 rabbitnet peripheral cards .............................................................................................. ........144 f.2 physical implementation ................................................................................................... ...............145 f.2.1 control and routing..................................................................................................... .............145 f.3 function calls............................................................................................................ .......................146 f.3.1 status byte ............................................................................................................. ...................152 index 153 rabbitcore rcm3365/RCM3375 schematics 157 user?s manual 1 1. i ntroduction the rcm3365 and RCM3375 rabbitcore modules feature a compact module that incorporates the latest revision of the power- ful rabbit ? 3000 microprocessor, flash memory, mass storage (nand flash), static ram, and digital i/o ports. the rcm3365 and RCM3375 present a new form of embedded flexibility with removable (?hot-swappable?) memory cards. the rcm3365 and RCM3375 both have an integrated 10/100base-t ethernet port, and provide for lan and internet-e nabled systems to be built as easily as serial-communication systems. in addition to the features already me ntioned above, the rcm3365 and RCM3375 have two clocks (main oscillator and real-time clock) , reset circuitry, and the circuitry necessary for management of battery backup of the rabbit 3000?s internal real-time clock and the static ram. two 34-pin headers bring out the rabbit 3000 i/o bus lines, parallel ports, and serial ports. the rcm3365/RCM3375?s mass-storage capabilitie s make them suited to running the optional dynamic c fat file system module wh ere data are stored and handled using the same directory file structure commonly used on pcs. a removable xd-picture card can be hot-swapped to transfer data quickly and ea sily using a standardized file system that can be read away from the rcm3365/RCM3375 installation. the rcm3365 or RCM3375 receives +3.3 v power from the customer-supplied mother- board on which it is mounted. the rcm3365 and RCM3375 can interface with all kinds of cmos-compatible digital devices through the motherboard. the development kit has what you need to design your own microprocessor-based system: a complete dynamic c software de velopment system including the dynamic c fat file system module, and a prototyping board that allows you to evaluate the rcm3365 or RCM3375, and to prototype circuits that interface to the rcm3365 or RCM3375 module. 2 rabbitcore rcm3365/RCM3375 1.1 rcm3365 and RCM3375 features ? small size: 1.85" x 2.73" x 0.86" (47 mm x 69 mm x 22 mm) microprocessor: rabbit 3000 running at 44.2 mhz 52 parallel 5 v tolerant i/o lines: 44 configurable for i/o, 4 fixed inputs, 4 fixed outputs three additional digital inputs, two additional digital outputs external reset alternate i/o bus can be configured for 8 da ta lines and 6 address lines (shared with parallel i/o lines), plus i/o read/write ten 8-bit timers (six cascadable) and one 10-bit timer with two match registers 512k flash memory, 512k program execution sram, 512k data sram fixed and hot-swappable mass-storage flash- memory options, which may be used with the standardized directory structure supported by the dynamic c fat file system module. real-time clock watchdog supervisor provision for customer-supplied backup ba ttery via connections on header j4 10-bit free-running pwm counter and four pulse-width registers two-channel input capture (shared with parallel i/o ports) can be used to time input signals from various port pins two-channel quadrature decoder accepts i nputs from external incremental encoder modules five or six 3.3 v cmos-compatible serial ports with a maximum asynchronous baud rate of 5.525 mbps . three ports are configurable as a clocked serial port (spi), and two ports are configurable as sdlc/hdlc seri al ports (shared with parallel i/o ports). supports 1.15 mbps irda transceiver supports dynamic c rabbi tsys, which supports ethernet access for remote application updates, and remote monitoring and control of a rabbitsys-enabled rcm3365 the rcm3900/rcm3910 and rcm3365/RCM3375 rabbitcore modules are similar to the rcm3305/rcm3315 and rcm3309/rcm3319, but they use fixed nand or remov- able media for their mass-storage memories inst ead of the fixed serial flash options of the rcm3305/rcm3315 and the rcm3309/rcm3319. user?s manual 3 table 1 below summarizes the main features of the rcm3365 and the RCM3375 modules. note: m-type xd-picture cards are not supported at this time. the rcm3365 and RCM3375 are programmed over a standard pc serial port through a serial programming cable supplied with the de velopment kit, and can also be programed through a usb port with an rs-232/usb converter, or directly over an ethernet link using the dynamic c download manager with or without a rabbitlink; dynamic c rabbitsys may also be used with a rabbitsys-enabled rcm3365 over an ethernet link. appendix a provides detailed specifications for the rcm3365 and the RCM3375. table 1. rcm3365/RCM3375 features feature rcm3365 RCM3375 microprocessor rabbit 3000 running at 44.2 mhz sram 512k program (fast sram) + 512k data flash memory (program) 512k flash memory (mass data storage) 32mb (fixed) * + up to 128mb (removable) (nand flash) * rcm3365 modules sold before 2008 had 16mb fixed nand flash memory. up to 128mb (removable) (nand flash) serial ports 6 shared high-speed, 3.3 v cmos-compatible ports: ? all 6 are configurable as asynchronous serial ports; ? 4 are configurable as a clocked serial port (spi) and 1 is configurable as an hdlc serial port; ? option for second hdlc serial port at the expense of 2 clocked serial ports (spi) 4 rabbitcore rcm3365/RCM3375 1.2 comparing the rcm3900/rcm3910 and rcm3365/RCM3375 we can no longer obtain certain components for the rcm3365/RCM3375 rabbitcore modules that support the originally specified -40c to +70c temperature range. instead of changing the design of the rcm3365/RCM3375 rabbitcore modules to handle available components specified for the original temperature range, we decided to develop a new product line ? the rcm3900 series. the rcm3900 series of rabbitcore modules is similar in form, dimensions, and function to the rcm3365/RCM3375 modules. we strongly recommend that existing rcm3365/ 3375 customers and designers of new systems consider using the new rcm3900 series rabbitcore modules. this section compares the two lines of rabbitcore modules. temperature specifications ? rcm3365/RCM3375 rabbitcore modules manufac- tured after may, 2008, are specified to operate at 0c to +70c. the rcm3900/ rcm3910, rated for -20c to +85c, are offered to customers requiring a larger temperature range after may, 2008. removable mass storage ? the hot-swappable xd-picture card ? mass storage device with up to 128mb of memory has been replaced with the minisd card with up to 1gb of memory. the minisd card is more readily availabl e today, and is expected to remain readily available for a long time. in addition, minisd card s provide a signif- icantly larger memory capacity, which has been requested by customers. the trade-off for the larger memory capacity is that the data transfer rate to/from the minisd card is about an order of magnitude slower than to/from the xd-picture card . note: rcm3365/RCM3375 rabbitcore modules may eventually be discontinued because of changes to the xd-picture card? . serial ports ? serial port b, available as either a clocked serial port or an asynchro- nous serial port on the rcm3365/RCM3375, is used by the rcm3900/rcm3910 as a clocked serial peripheral interface (spi) for the minisd? card , and is not brought out for customer use. general-purpose i/o ? pd2, a configurable i/o pin on the rcm3365/RCM3375, is used to enable/disable the rabbitnet spi interface when the rcm3365/RCM3375 is installed on the prototyping board. the rcm3900/rcm3900 use pd2 to detect whether the minisd? card is installed, and so pd2 is not brought out for customer use on the rcm3900/rcm3910. maximum current ? the rcm3365/RCM3375 draws 250 ma vs. the 325 ma required by the rcm3900/rcm3910. leds ? the speed and user ( usr / bsy )led locations have been swapped between the rcm3365/RCM3375 and the rcm3900/rcm3910, the lnk / act leds have been combined to one led on the rcm3900/rcm3910, and the rcm3900/rcm3910 has an fdx / col led instead of the fm led on the rcm3365/RCM3375. the led placements on the boards remain unchanged. user?s manual 5 ethernet chip ? a different ethernet controller chip is used on the rcm3900/ rcm3910. the ethernet chip is able to dete ct automatically whether a crossover cable or a straight-through cable is being used in a particular setup, and will configure the signals on the ethernet jack interface. dynamic c ? as long as no low-level fat file system calls or direct xd-picture card access calls to the nflash.lib library were used in your application developed for the rcm3365/RCM3375, you may run that application on the rcm3900/rcm3910 after you recompile it using dynamic c v. 9.60. note: the dynamic c rabbitsys option for programming an rcm3365 over an ethernet link is not supported for the rcm3900. 1.3 advantages of the rcm3365 and RCM3375 fast time to market using a fully engineer ed, ?ready-to-run/ready-to-program? micro- processor core. competitive pricing when compared with th e alternative of purchasing and assembling individual components. easy c-language program development and debugging program download utility (rabbit field utility) and cloning board options for rapid production loading of programs. generous memory size allows large programs with tens of thousands of lines of code, and substantial data storage. integrated ethernet port for network connec tivity, with royalty-free tcp/ip software. ideal for network-enabling security and access systems, home automation, hvac systems, and industrial controls 6 rabbitcore rcm3365/RCM3375 1.4 development and evaluation tools 1.4.1 rcm3365/RCM3375 development kit the rcm3365/RCM3375 development kit contains the hardware you need to use your rcm3365 or RCM3375 module. rcm3365 module. prototyping board. ac adapter, 12 v dc, 1 a (included only with development kits sold for the north amer- ican market). a header plug leading to bare leads is provided to allow overseas users to connect their own power supply with a dc output of 8?30 v.) serial programming cable with 10-pin header and de9 connections. 2 cds ? dynamic c ? and dynamic c fat file system module ? with complete product documentation on disk. getting started instructions. 32 mb xd-picture card? . accessory parts for use on the prototyping board. screwdriver and ethernet cables. rabbit 3000 processor easy reference poster. registration card. figure 1. rcm3365/RCM3375 development kit rabbit and dynamic c are registered trademarks of rabbit semiconductor inc. rabbitcore rcm3365/RCM3375 development kit contents the rcm3365/RCM3375 development kit contains the following items: ? rcm3365 module. ? rcm3300 prototyping board. ? ac adapter, 12 v dc, 1 a. (included only with development kits sold for the north american market. a header plug leading to bare leads is provided to allow overseas users to connect their own power supply with a dc output of 8?30 v.) ? 10-pin header to db9 programming cable with integrated level-matching circuitry. ? 2 cds ? dynamic c and dynamic c fat file system module ? with complete product documentation on disk. ? ethernet cables and screwdriver. ? getting started instructions. ? 32 mb xd-picture card ? (nand flash) ? a bag of accessory parts for use on the prototyping board. ? rabbit 3000 processor easy reference poster. ? registration card. installing dynamic c ? insert the cd from the development kit in your pc?s cd-rom drive. if the instal- lation does not auto-start, run the setup.exe program in the root directory of the dynamic c cd. install any dynamic c modules after you install dynamic c. ! " # " $ " % & ' # $ % ( " )) &* &( )$ )+ $' &, )% -% )* )( !( " . # /# # & /& & # ".! . * #0 #0 1 " ! " ' " & " ) " + $ # ' & ) + #0 0#+ ' # & $ ) % + ( 0#% ' # & $ ! " . " ' 2% 3 $ ' 1 0#( 4#& 4## )& )# &' #, )' $, ! " 5 ! 6 / " / 0( & ( $ ) % + , * 4+ #' + # # 0& 0# 0) 0+ $ & # '%1 %1 -&-#-# 0% 1/7/# 1/ 1/ 1/7 0$ & 0# $ 0& 1 "! !/' % ( "# ") "+ 5( 5% ( % $ ' 0* $2$1 1/ !/"# ) + "' "$ "% + ) & 5 ) 5 + " ( /$$'' . !# "!" 0, !& !$ ( $ % $ # ( % $ # 5' 5& ' & ) + ! + & ) & ' + ) & ' 5# 5$ # $ % ( 0 0 ! # # & * # ## 0$ #& , #& 0) 0#' # & #) % # #$ 4% #+ #% #( '' '# '& '$ ') '% '+ '( 4 4 ) #$ 4# 4& &,$ 681" &,$ 681" 4* &% &+ &( &* 0#) &) 4#' $* $( $% &+ 0% $+ &$ &# 4, && 0#$ $$ $) #( #* 49% 49# !&': 49& !&': 9& &% 0#& %' -+ ), ) % + ( &, $' $# $& " !& !$ !) !% !+ ;";" ;5;5)*% )*%7 -# -& -$ -) #+ &) &$ && &# "/4 " " 4) $2$1 %1 $2$1 %1 4$ 49) 9# 9#+ 9#( 9#$ 9#) 9#* 9#% 5'< 5'<- 0## ( 4( #* #, &' #) #% 9# 9& % % % + % ( % * + $ + ) + % + + %, +& %# %) ! &$8+ ! &$8+ +( +* +, (' !" user?s manual 7 1.4.2 software the rcm3365 and the RCM3375 are programmed using version 9.24 or later of dynamic c. a compatible version is included on the development kit cd-rom. rabbit is also offering rcm3365 rabbitcore m odules preloaded with dynamic c rabbit- sys firmware to allow these modules to r un dynamic c rabbitsys. dynamic c rabbitsys requires dynamic c version 9.30 or later, and allows the rcm3365 to be accessed via an ethernet connection for remote application updates, and for remote monitoring and con- trol. a rabbitsys development kit is availabl e with all the hardware and software tools that are needed to develop a rabbitsys application. dynamic c v. 9.60 includes the popular c/os -ii real-time operating system, point-to- point protocol (ppp), fat file system, rabbi tweb, and other select libraries that were previously sold as individual dynamic c modules. rabbit also offers for purchase the rabbit em bedded security pack featuring the secure sockets layer (ssl) and a specific advanced encryption standard (aes) library. in addi- tion to the web-based technical support incl uded at no extra charge, a one-year telephone- based technical support subscription is also av ailable for purchase. visit our web site at www.rabbit.com for further information and complete documentation, or contact your rabbit sales representative or authorized distributor. note: version 2.10 or later of the dynamic c fat file system module is required to use the fat file system with the rcm3365 and RCM3375 models. 1.4.3 accessories rabbit has available a usb removable memory card reader and a connector adapter board. usb removable memory card reader (part no. 20-101-1104)?allows you to read data from the xd-picture card via your pc. connector adapter board (part no. 151-0114)?allows you to plug the rcm3365/ RCM3375 whose headers have a 2 mm pitch into header sockets with a 0.1" pitch. visit our web site at www.rabbit.com or contact your rabbit sale s representative or autho- rized distributor for further information. 1.4.4 online documentation the online documentation is installed along with dynamic c, and an icon for the docu- mentation menu is placed on the workstation?s desktop. double-click this icon to reach the menu. if the icon is missing, use your browser to find and load default.htm in the docs folder, found in the dynamic c installation folder. the latest versions of all documents are al ways available for free, unregistered download from our web sites as well. 8 rabbitcore rcm3365/RCM3375 user?s manual 9 2. g etting s tarted this chapter explains how to set up and use the rcm3365/ RCM3375 modules with the accompanying prototyping board. note: it is assumed that you have a development kit. if you purchased an rcm3365 or RCM3375 module by itself, you will have to adapt the information in this chapter and elsewhere to your test and development setup. 2.1 install dynamic c to develop and debug programs for the rcm3365/RCM3375 (and for all other rabbit hardware), you must install and use dynamic c. if you have not yet installed dynamic c vers ion 9.24 (or a later version), do so now by inserting the dynamic c cd from the developm ent kit in your pc?s cd-rom drive. if autorun is enabled, the cd installation will begin automatically. if autorun is disabled or the installation otherwise does not start, use the windows start | run menu or windows disk explorer to launch setup.exe from the root folder of the cd-rom. the installation program will guide you through th e installation process. most steps of the process are self-explanatory. dynamic c uses a com (serial) port to communicate with the target development system. the installation allows you to choose the com port that will be used. the default selec- tion is com1. you may select any available port for dynamic c?s use. if you are not cer- tain which port is available, select com1. this selection can be changed later within dynamic c. note: the installation utility does not check the selected com port in any way. speci- fying a port in use by another device (mouse, modem, etc.) may lead to a message such as "could not open serial port" when dynamic c is started. once your installation is complete, you will have up to three icons on your pc desktop. one icon is for dynamic c, one opens the documentation menu, and the third is for the rabbit field utility, a tool used to downloa d precompiled software to a target system. if you have purchased the optional dynamic c rabbit embedded security pack, install it after installing dynamic c. you must install the rabbit embedded security pack in the same directory where dynamic c was installed. 10 rabbitcore rcm3365/RCM3375 2.2 hardware connections there are three steps to connecting the prototyping board for use with dynamic c and the sample programs: 1. attach the rcm3365/RCM3375 module to the prototyping board. 2. connect the serial programming cable between the rcm3365/RCM3375 and the worksta- tion pc or if you have an rcm3365 with rabbitsys firmware you may connect the rcm3365 and the pc using ethernet cables. 3. connect the power supply to the prototyping board. 2.2.1 step 1 ? attach module to prototyping board turn the rcm3365/RCM3375 module so that the ethernet jack is facing the direction shown in figure 2 below. align the pins from headers j3 and j4 on the bottom side of the module into header sockets ja and jb on the prototyping board. the picture card (nand flash) does not have to be inserted into connector j6 on the rcm3365/RCM3375 at this time. figure 2. install the rcm3365/RCM3375 module on the prototyping board note: it is important that you line up the pins on headers j3 and j4 of the rcm3365/ RCM3375 module exactly with the corresponding pins of header sockets ja and jb on the prototyping board. the header pins may become bent or damaged if the pin align- ment is offset, and the module will not work. permanent electrical damage to the mod- ule may also result if a misaligned module is powered up. press the module?s pins firmly into the prototyping board header sockets?press down in the area above the header pins usi ng your thumbs or fingers over the header pins as shown in figure 2. do not press down on the picture card connector (j6) unless the picture card is installed, but rather press down on the circuit board along the edge by the connector. also, do not press down on the middle of the module to avoid flexing the module, which could damage the module or components on the module. should you need to remove the module, grasp it with your fingers along the sides by the con- nectors and gently work the module up to pull the pins away from the sockets where they are installed. do not remove the module by grasping it at the top and bottom. ! "# "$ "% & ' # $ % ( " )) &* &( )$ )+ $' &, )% -% )* )( !( " . # /# # & /& & # ".! . * #0 #0 1 "! "' "& ") "+ $ # ' & ) + #0 0#+ ' # & $ ) % + ( 0#% ' # & $ ! " . " '2%3$'1 0#( 4#& 4## )& )# &' #, )' $, !" 5 !6 /"/ 0( & ( $ ) % + , * 4+ #' + # # 0& 0# 0) 0+ $ & # '%1 %1 -& -#-# 0% 1/7 /# 1/ 1/ 1/7 0$ & 0# $ 0& 1 "! !/' % ( "# ") "+ 5( 5% ( % $ ' 0* $2$1 1/ !/"# ) + "' "$ "% + ) & 5)5+"( /$$'' . !# "!" 0, !& !$ ( $ % $ # ( % $ # 5' 5& ' & ) + ! + & ) & ' + ) & ' 5# 5$ # $ % ( 0 0 !# # & * # ## 0$ #& , #& 0) 0#' # & #) % # #$ 4% #+ #% #( '' '# '& '$ ') '% '+ '( 4 4 ) #$ 4# 4& &,$ 681" &,$ 681" 4* &% &+ &( &* 0#) &) 4#' $* $( $% &+ 0% $+ &$ &# 4, && 0#$ $$ $) #( #* 49% 49# !&': 49& !&': 9& &% 0#& %' -+ ), ) % + ( &, $' $# $& " !& !$ !) !% !+ ;";" ;5;5)*% )*%7 -# -& -$ -) #+ &) &$ && &# "/4 " " 4) $2$1 %1 $2$1 %1 4$ 49) 9# 9#+ 9#( 9#$ 9#) 9#* 9#% 5'< 5'<- 0## ( 4( #* #, &' #) #% 9# 9& %% %+ %( %* +$ +) +% ++ %, +& %# %) ! &$8+ ! &$8+ +( +* +, (' !& $% $+ $( $* )$ !) 4#$ *# (* () # #) #% &+ &( #$ 4& #& ## 0# #' # + * #' ## #% #, &' &) &* $% (( (, (& (' (# *& $# %$ %) )) %* $) &' &# $+ &% &( &# #* #& #$ , 4$ ( & $ + .# , *) ) & % 4# % *' *% (' *+ +) (( %' &, 0, %, #') 4% +( )% #) 4+ 4) #* && 0+ 0( 0* 0) 0% && 0+ ) (, # )& *# *+ (+ 0& $' *& .& -& ,+ +( #'% !$ !# +# &$ 4#+ ) & #! $ %&&'() $ %&&*( " + user?s manual 11 2.2.2 step 2 ? connect serial programming cable the serial programming cable connects the rcm3365/RCM3375 to the pc running dynamic c to download programs and to monitor the module during debugging. connect the 10-pin connector of the serial programming cable labeled prog to header j1 on the rcm3365/RCM3375 module as shown in figure 3. there is a small dot on the cir- cuit board next to pin 1 of header j1. be sure to orient the marked (usually red) edge of the cable towards pin 1 of the connector. (do not use the diag connector, which is used for a nonprogramming serial connection.) figure 3. connect serial programming cable and power supply note: be sure to use the serial programming cable (part number 101-0542) supplied with this development kit?the serial programming cable has blue shrink wrap around the rs-232 converter section located in the middle of the cable. programming cables with clear or red shrink wrap from other rabbit kits are not designed to work with rcm3365/ RCM3375 modules. connect the other end of the serial programming cable to a com port on your pc. note: some pcs now come equipped only with a usb port. it may be possible to use an rs-232/usb converter (part no. 20-151--0178) with the serial programming cable supplied with the rcm3365/RCM3375 development kit. note that not all rs-232/ usb converters work with dynamic c. ! "# "$ "% & ' # $ % ( " )) &* &( )$ )+ $' &, )% -% )* )( !( " . # /# # & /& & # ".! . * #0 #0 1 "! "' "& ") "+ $ # ' & ) + #0 0#+ ' # & $ ) % + ( 0#% ' # & $ ! " . " '2%3$'1 0#( 4#& 4## )& )# &' #, )' $, !" 5 !6 /"/ 0( & ( $ ) % + , * 4+ #' + # # 0& 0# 0) 0+ $ & # '%1 %1 -&-#-# 0% 1/7/# 1/ 1/ 1/7 0$ & 0# $ 0& 1 "! !/' % ( "# ") "+ 5( 5% ( % $ ' 0* $2$1 1/ !/"# ) + "' "$ "% + ) & 5)5+"( /$$'' . !# "!" 0, !& !$ ( $ % $ # ( % $ # 5' 5& ' & ) + ! + & ) & ' + ) & ' 5# 5$ # $ % ( 0 0 !# # & * # ## 0$ #& , #& 0) 0#' # & #) % # #$ 4% #+ #% #( '' '# '& '$ ') '% '+ '( 4 4 ) #$ 4# 4& &,$ 681" &,$ 681" 4* &% &+ &( &* 0#) &) 4#' $* $( $% &+ 0% $+ &$ &# 4, && 0#$ $$ $) #( #* 49% 49# !&': 49& !&': 9& &% 0#& %' -+ ), ) % + ( &, $' $# $& " !& !$ !) !% !+ ;";" ;5;5)*% )*%7 -# -& -$ -) #+ &) &$ && &# "/4 " " 4) $2$1 %1 $2$1 %1 4$ 49) 9# 9#+ 9#( 9#$ 9#) 9#* 9#% 5'< 5'<- 0## ( 4( #* #, &' #) #% 9# 9& %% %+ %( %* +$ +) +% ++ %, +& %# %) ! &$8+ ! &$8+ +( +* +, (' !& $% $+ $( $* )$ !) 4#$ *# (* () # #) #% &+ &( #$ 4& #& ## 0# #' # + * #' ## #% #, &' &) &* $% (( (, (& (' (# *& $# %$ %) )) %* $) &' &# $+ &% &( &# #* #& #$ , 4$ ( & $ + .# , *) ) & % 4# % *' *% (' *+ +) (( %' &, 0, %, #') 4% +( )% #) 4+ 4) #* && 0+ 0( 0* 0) 0% && 0+ ) (, # )& *# *+ (+ 0& $' *& .& -& ,+ +( #'% !$ !# +# &$ 4#+ ) & ==> ? 0# @ a ? 12 rabbitcore rcm3365/RCM3375 2.2.2.1 programming via ethernet option an ethernet cable connects a rabbitsys-enabled rcm3365 to the pc running dynamic c with dynamic c rabbitsys via a dhcp netw ork to download programs and to monitor the rcm3365 module during debugging. use a straight-through cat 5/6 ethernet cable to connect the ethernet jack on the rcm3365 to a dhcp-enabled network. your pc should al so be connected to this network?you will need a second straight-t hrough cat 5/6 ethernet cable to connect the pc to the network since only one straight-through ethernet cable is supplied with the development kit. figure 4. connect ethernet cable for ethernet programming option you may also use a crossover cat 5/6 ethernet cable to connect the ethernet jack on the rcm3365 directly to your pc, but there will be additional steps required to configure the tcp/ip parameters on the rcm3365 and on your pc if your pc does not have a dhcp server. these steps are described in appendix e. ! "# "$ "% & ' # $ % ( " )) &* &( )$ )+ $' &, )% -% )* )( !( " . # /# # & /& & # ".! . * #0 #0 1 "! "' "& ") "+ $ # ' & ) + #0 0#+ ' # & $ ) % + ( 0#% ' # & $ ! " . " '2%3$'1 0#( 4#& 4## )& )# &' #, )' $, !" 5 !6 /"/ 0( & ( $ ) % + , * 4+ #' + # # 0& 0# 0) 0+ $ & # '%1 %1 -&-#-# 0% 1/7 /# 1/ 1/ 1/7 0$ & 0# $ 0& 1 "! !/' % ( "# ") "+ 5( 5% ( % $ ' 0* $2$1 1/ !/"# ) + "' "$ "% + ) & 5)5+"( /$$'' . !# "!" 0, !& !$ ( $ % $ # ( % $ # 5' 5& ' & ) + ! + & ) & ' + ) & ' 5# 5$ # $ % ( 0 0 !# # & * # ## 0$ #& , #& 0) 0#' # & #) % # #$ 4% #+ #% #( '' '# '& '$ ') '% '+ '( 4 4 ) #$ 4# 4& &,$ 681" &,$ 681" 4* &% &+ &( &* 0#) &) 4#' $* $( $% &+ 0% $+ &$ &# 4, && 0#$ $$ $) #( #* 49% 49# !&': 49& !&': 9& &% 0#& %' -+ ), ) % + ( &, $' $# $& " !& !$ !) !% !+ ;";" ;5;5)*% )*%7 -# -& -$ -) #+ &) &$ && &# "/4 " " 4) $2$1 %1 $2$1 %1 4$ 49) 9# 9#+ 9#( 9#$ 9#) 9#* 9#% 5'< 5'<- 0## ( 4( #* #, &' #) #% 9# 9& %% %+ %( %* +$ +) +% ++ %, +& %# %) ! &$8+ ! &$8+ +( +* +, (' !& $% $+ $( $* )$ !) 4#$ *# (* () # #) #% &+ &( #$ 4& #& ## 0# #' # + * #' ## #% #, &' &) &* $% (( (, (& (' (# *& $# %$ %) )) %* $) &' &# $+ &% &( &# #* #& #$ , 4$ ( & $ + .# , *) ) & % 4# % *' *% (' *+ +) (( %' &, 0, %, #') 4% +( )% #) 4+ 4) #* && 0+ 0( 0* 0) 0% && 0+ ) (, # )& *# *+ (+ 0& $' *& .& -& ,+ +( #'% !$ !# +# &$ 4#+ ) & ,()' !" a user?s manual 13 2.2.3 step 3 ? connect power when all other connections have been made , you can connect power to the prototyping board. connect the wall transformer to jack j1 on the prototyping board as shown in figure 3. plug in the wall transformer. the core led on the prototyping board should light up . the rcm3365/RCM3375 and the prototyping board are now ready to be used. note: a reset button is provided on the prototyping board to allow a hardware reset without disconnecting power. the rcm3365/RCM3375 can also be reset from dynamic c by pressing 14 rabbitcore rcm3365/RCM3375 2.3 starting dynamic c once the rcm3365/RCM3375 is connected as described in the preceding pages, start dynamic c by double-clicking on the dynami c c icon on your desktop or in your start menu. select code and bios in flash, run in ram on the ?compiler? tab in the dynamic c options > project options menu. click ok . section 2.3.1 explains the remaining dynamic c configurations to r un a sample program via the serial programming cable, and sec tion 2.3.2 explains the remaining dynamic c configurations to run a sample program via an ethernet cable. user?s manual 15 2.3.1 running dynamic c via serial programming cable dynamic c uses the serial port on your pc that you specified during installation. if you are using a usb port to connect your computer to the rcm3365/RCM3375 module, choose options > project options and select ?use usb to serial converter? on the communications tab. 2.3.1.1 run a sample program use the file menu to open the sample program pong.c , which is in the dynamic c samples folder. press function key f9 to compile and run the program. the stdio window will open on your pc and will display a small square bouncing around in a box. this program shows that the cpu is working. the sample program described in section 6.5, ?run the pingme.c sample program,? tests the tcp/ip portion of the board. 2.3.1.2 troubleshooting if dynamic c cannot find the target system (error message "no rabbit processor detected." ): check that the rcm3365/RCM3375 is powered correctly ? the red core led on the prototyping board should be lit when the rcm3365/RCM3375 is mounted on the prototyping board and the ac adapter is plugged in . check both ends of the programming cable to ensure that they are firmly plugged into the pc and the prog connector, not the diag connector, is plugged in to the program- ming port on the rcm3365/RCM3375 with the marked (colored) edge of the program- ming cable towards pin 1 of the programming header. ensure that the rcm3365/RCM3375 module is firmly and correctly installed in its connectors on the prototyping board. dynamic c uses the com port specified dur ing installation. select a different com port within dynamic c. from the options menu, select project options , then select communications . select another com port from the list, then click ok. press 16 rabbitcore rcm3365/RCM3375 2.3.2 running dynamic c via ethernet cables the firmware needed to run rabbitsys has been preloaded on rcm3365 rabbitcore modules sold for use with dynamic c rabbits ys. the software from the dynamic c and the dynamic c rabbitsys cds must be installed on your pc. a system running rabbitsys can be connected to a dhcp network using st raight-through ethernet cables, or it can be connected directly to the pc via an ethernet crossover cable. if you are connecting to a network with a dhcp server, use a cat 5/6 straight-through ethernet cable to connect the pc or wo rkstation to the network, and connect the ethernet jack on the rcm3365 to the network using a second cat 5/6 straight-through ethernet cable. if your pc or workstation is running a dhcp server, connect the cat 5/6 ethernet crossover cable from the pc or workstati on directly to the ethernet jack on the rcm3365. follow the instructions below for a straight-through ethernet cable. tip: it is recommended that you use one of the above options for a pc/workstation or network with a dhcp server or the serial cable programming option when you are using the rcm3365 for the first time since these options are easier to set up and run. if your pc/workstation does not have a dhcp se rver, you will have to enter the tcp/ip parameters into the rcm3365 module and on to the pc, notebook, or workstation. see appendix e for more information on this option. using dhcp network with straight-through ethernet cables enable separate instruction and data spaces a nd select ?compile program in rabbitsys user mode? from the dynamic c options > project options > compiler menu. before you compile and run a program via the ethernet for the first time via a dhcp net- work, you must run the rdiscover utility by double-clicking it on your pc desktop. your pc must be connected to the same dhcp network as the rcm3365. the utility will open a window and list the mac addresses for any ra bbitsys boards connected to the network. select a board from the list to display additi onal information such as the board?s internet address. this is the ip address to enter when you access the dynamic c options > project options > communications menu to select ?use tcp/ip connection.? you must also enter ?32023? for the control port and the de fault login values of ?admin? and ?pass- word.? 2.3.2.1 run a sample program use the file menu to open the sample program pong.c , which is in the dynamic c samples folder. press function key f9 to compile and run the program. the stdio window will open on your pc and will display a small square bouncing around in a box. this program shows that the cpu is working. the sample program described in section 6.5, ?run the pingme.c sample program,? tests the tcp/ip portion of the board. user?s manual 17 2.3.2.2 troubleshooting if the rdiscover utility could not find your rcm3365: check that your network has a dhcp server, and that the rcm3365 and your pc are connected to the same network. if you compiled and ran a sample program with the rabbitsys project option disabled, you may have overwritten the rabbitsys bina ry file. use the serial programming cable to connect programming header j1 on th e rcm3365 to your pc com port to reload the rabbitsys binary file via the dynamic c compile > reload rabbitsys binary menu. if the rdiscover utility could not find your rcm3365, and you were unable to reload the rabbitsys binary file, your rcm3365 does not have the firmware to support dynamic c rabbitsys and cannot be used with dynamic c rabbitsys. if dynamic c returns an error message, check that the rcm3365 is powered correctly. the red core led on the prototyping board should be lit when the rcm3365 is mounted on the prototyping board and the ac adapter is plugged in. ensure that the rcm3365 mod- ule is firmly and correctly installed in its connectors on the prototyping board. 2.4 where do i go from here? if the sample program ran fine, you are now r eady to go on to other sample programs and to develop your own applications. the source code for the sample programs is provided to allow you to modify them for your own use. the rcm3365/RCM3375 user?s manual also provides complete hardware reference in formation and describes the software func- tion calls for the rcm3365 and the RCM3375, the prototyping board, and the optional lcd/keypad module. for advanced development topics, refer to the dynamic c user?s manual , the dynamic c rabbitsys user?s manual , and the dynamic c tcp/ip user?s manual , also in the online documentation set. 2.4.1 technical support note: if you purchased your rcm3365/RCM3375 through a distributor or through a rabbit partner, contact the distributor or partner first for technical support. if there are any problems at this point: use the dynamic c help menu to get further assistance with dynamic c. check the rabbit technical bulletin board and forums at www.rabbit.com/support/bb/ and at www.rabbit.com/forums/ . use the technical support e-mail form at www.rabbit.com/support/ . 18 rabbitcore rcm3365/RCM3375 user?s manual 19 3. r unning s ample p rograms to develop and debug programs for the rcm3365/RCM3375 (and for all other rabbit hardware), you must install and use dynamic c. 3.1 introduction to help familiarize you with the rcm3365 and RCM3375 modules, dynamic c includes several sample programs. loading, executi ng and studying these programs will give you a solid hands-on overview of the rcm3365/RCM3375?s capabilities, as well as a quick start using dynamic c as an application development tool. note: the sample programs assume that you have at least an elementary grasp of the c programming language. if you do not, see the introductory pages of the dynamic c user?s manual for a suggested reading list. more complete information on dynamic c is provided in the dynamic c user?s manual . in order to run the sample programs discussed in this chapter and elsewhere in this manual, 1. your rcm3365/RCM3375 module must be plugged in to the prototyping board as described in chapter 2, ?getting started.? 2. dynamic c must be installed and running on your pc. 3. the rcm3365/RCM3375 module must be connected to your pc either through the serial programming cable or through an ethernet cable/network if you have a rabbitsys-enabled rcm3365. 4. power must be applied to the rcm3365/RCM3375 through the prototyping board. refer to chapter 2, ?getting started,? if you need further information on these steps. since the rcm3365 and the RCM3375 run at 44.2 mhz and are equipped with a fast pro- gram execution sram, remember to allow the compiler to run the application in the fast program execution sram by selecting code and bios in flash, run in ram from the dynamic c options > project options > compiler menu. to run a sample program, open it with the file menu, then press function key f9 to com- pile and run the program. 20 rabbitcore rcm3365/RCM3375 3.2 sample programs of the many sample programs included with dynamic c, several are specific to the rcm3365 and the RCM3375. sample programs illu strating the general operation of the rcm3365/RCM3375, serial communication, and the nand flash are provided in the samples\rcm3360 folder. each sample program has comments that describe the purpose and function of the program. follow the instru ctions at the beginning of the sample pro- gram. note that the rcm3365/RCM3375 must be installed on the prototyping board when using the sample programs described in this chapter. controlled.c ?demonstrates use of the digital inputs by having you turn the leds on the prototyping board on or off from the stdio window on your pc. once you compile and run controlled.c , the following display will appear in the dynamic c stdio window. press ?2? or ?3? or ?4?or ?5?on your keyboard to select led ds3 or ds4 or ds5 or ds6 on the prototyping board. then follow the prompt in the dynamic c stdio win- dow to turn the led on or off. flashled.c ?demonstrates assembly-language program by flashing the usr led on the rcm3365/RCM3375 and leds ds3, ds4, ds5, and ds6 on the prototyping board. swrelay.c ?demonstrates the relay-switching f unction call using th e relay installed on the prototyping board through screw-terminal header j17. toggleswitch.c ?uses costatements to detect switches s2 and s3 using debounc- ing. the corresponding leds (ds3 and ds4) will turn on or off. once you have loaded and executed these four programs and have an understanding of how dynamic c and the rcm3365/RCM3375 modules interact, you can move on and try the other sample programs, or begin building your own. user?s manual 21 3.2.1 use of nand flash the following sample programs can be found in the samples\rcm3360\nandflash folder. as you run most of these sample programs, you will be prompted in the dynamic c stdio win- dow to select either the soldered-in nand flash (rcm3365 model only) or the socketed xd-picture card (0 = soldered, 1 = socketed). nflash_dump.c ?this program is a utility for dumping the nonerased contents of a nand flash chip to the dynamic c stdio window, and the contents may be redi- rected to a serial port. when the sample program starts running, it attempts to communicate with the user- selected nand flash chip. if this communication is successful and the main page size is acceptable, the nonerased page contents (non 0xff) from the nand flash page are dumped to the dynamic c stdio win.for inspection. note that an error message might appear when the first 32 pages (0x20 pages) are ?dumped.? you may ignore the error message. nflash_inspect.c ?this program is a utility for inspecting the contents of a nand flash chip. when the sample program starts running, it attempts to communi- cate with the nand flash chip selected by the user. once a nand flash chip is found, the user can execute various commands to pr int out the contents of a specified page, clear (set to zero) all the bytes in a specified page, erase (set to ff), or write to specified pages. caution: when you run this sample program, enabling the #define nflash_ canerasebadblocks macro makes it possible to write to bad blocks. the first two blocks on the xd-picture card are marked bad to protect the configuration data needed to use the card in a digital camera or a pc. you will only be able to use the xd-picture card in rabbit-based systems if either of the first two blocks is written to. nflash_log.c ?this program runs a simple web server and stores a log of hits in the nand flash. as long as the xd-picture card is plugged in to its connector j6, this sample program will log hits to the xd-picture card . remove the xd-picture card if you wish to log hits on the soldered-in nand flash (rcm3365 model only). this log can be viewed and cleared from a browser by connecting the rj-45 jack on the rcm3365 to your pc as described in section 6.1. the sidebar on the next page explains how to set up your pc or notebook to view this log. 22 rabbitcore rcm3365/RCM3375 as long as you have not modified the tcpconfig 1 macro in the sample program, enter the following server address in you r web browser to bring up the web page served by the sample program. http://10.10.6.100 otherwise use the tcp/ip settings you entered in the tcp_config.lib library. this sample program does not exhibit ideal behavior in its method of writing to the nand flash. however, the inefficiency attribut able to the small amount of data written in each append operation is offset somewhat by the expected relative infrequency of these writes, and by the sample program's method of ?walking? through the flash blocks when appending data as well as when a log is cleared. nflash_erase.c ?this program is a utility to erase all the good blocks on a nand flash chip. when the program starts running, it attempts to establish communication with the nand flash chip selected by the us er. if the communication is successful, the progress in erasing the blocks is displayed in the dynamic c stdio window as the blocks are erased. follow these instructions to set up your pc or notebook. check with your administra- tor if you are unable to change the setti ngs as described here since you may need administrator privileges. the instructions are specifically for windows 2000, but the interface is similar for other versions of windows. tip: if you are using a pc that is already on a network, you will disconnect the pc from that network to run these sample programs. write down the existing settings before changing them to facilitate restoring them when you are finished with the sample programs and reconnect your pc to the network. 1. go to the control panel ( start > settings > control panel ), and then double-click the network icon. 2. select the network interface card used for the ethernet interface you intend to use (e.g., tcp/ip xircom credit card network adapter ) and click on the ?proper- ties? button. depending on which version of windows your pc is running, you may have to select the ?local area connection? first, and then click on the ?properties? button to bring up the ethernet interface dialog. then ?configure? your interface card for a ?10base-t half-duplex? or an ?auto-negotiation? connection on the ?advanced? tab. note: your network interface card will likely have a different name. 3. now select the ip address tab, and check specify an ip address , or select tcp/ip and click on ?properties? to assign an ip a ddress to your computer (this will disable ?obtain an ip address automatically?): ip address : 10.10.6.101 netmask : 255.255.255.0 default gateway : 10.10.6.1 4. click user?s manual 23 3.2.2 hot-swapping xd-picture card the sample programs in this section require that you have insta lled the dynamic c fat file system module, which is included with the rcm3365/RCM3375 development kit. visit our web site at www.rabbit.com or contact your rabbit sale s representative or autho- rized distributor for further information on the dynamic c fat file system and other dynamic c modules. note: versions of the dynamic c fat file system prior to 2.10 did not use unique volume labels, so hot-swapping two xd-picture card that were both formatted with older versions of the fat file system may cause cache recovery errors the following sample program can be found in the samples\rcm3360\nandflash folder. since rabbit-based systems do not implement the xd-picture card ? specification for data storage, hot-swap only xd-picture cards that you plan to have formatted for use in rabbit-based systems. fat_hot_swap_3365_75.c ?this program demonstrates how to hot-swap the xd- picture card on the rcm3365/RCM3375. once you have compiled the sample program and it is running, press switch sw 3 on the prototyping board or press any keyboard key on your pc to signal your intent to do a hot-swap. remove the xd- picture card and insert a new xd-picture card (or replace the original one) when prompted to do so in the dynamic c stdio window or when the green led (ds4) on the prototyping board lights up. do not remove the xd-picture card until you are prompted or signaled by the led! the the xd-picture card can only be hot-swapped when the xd-picture card is ?unmounted.? this sample program ?unmounts? the xd-picture card when it detects a keyboard hit or sw3 press. then it waits for a new xd-picture card to be inserted. the following sample program can be found in the samples\filesystem\ folder. fat_hot_swap.c ?this program demonstrates how to hot-swap the xd-picture card on boards that support the xd-picture card and have their data bus buffered. once you have compiled the sample program and it is running, press any keyboard key on your pc to signal your intent to do a hot-swap. remove the xd-picture card and insert a new xd-picture card (or replace the original one) when prompted to do so in the dynamic c stdio window. do not remove the xd-picture card until you are prompted! the xd-picture card can only be hot-swapped when the xd-picture card is ?unmounted.? this sample program ?unmounts? the xd-picture card when it detects a keyboard press. then it waits for a new xd-picture card to be inserted. 24 rabbitcore rcm3365/RCM3375 3.2.3 serial communication the following sample programs can be found in the samples\rcm3360\serial folder. flowcontrol.c ?this program demonstrates hardwa re flow control by configuring serial port f for cts/rts with serial data coming from txe (serial port e) at 115,200 bps. one character at a time is received and is displayed in the stdio window. to set up the prototyping board, you will need to tie txe and rxe together on the rs-232 header at j14, and you will also tie txf and rxf together as shown in the diagram. a repeating triangular pattern should print out in the stdio window. the program periodically switches rts (txf) flow control on or off to demonstrate the effect of hardware flow control. parity.c ?this program demonstrates the use of parity modes by repeatedly sending byte values 0?127 from serial port e to seri al port f. the program will switch between generating parity or not on serial port e. serial port f will always be checking parity, so parity errors should occur during every other sequence. to set up the prototyping board, you will need to tie txe and rxf together on the rs-232 header at j14 as shown in the diagram. the dynamic c stdio window will display the error sequence. simple3wire.c ?this program demonstrates basic rs-232 serial communication. lower case characters are sent by txe, and are received by rxf. the characters are converted to upper case and are sent out by txf, are received by rxe, and are displayed in the dynamic c stdio window. to set up the prototyping board, you will need to tie txe and rxf together on the rs-232 header at j14, and you will also tie rxe and txf together as shown in the diagram. simple5wire.c ?this program demonstrates 5-wi re rs-232 serial communication by providing flow control (rts/cts) on serial port f and data flow on serial port e. to set up the prototyping board, you will need to tie txe and rxe together on the rs-232 header at j14, and you will also tie txf and rxf together as shown in the diagram. once you have compiled and run this program, you can test flow control by disconnecting txf from rxf while the program is running. char- acters will no longer appear in the stdio window, and will display again once txf is connected back to rxf. (do not disconnect the data path between txe and rxe.) -./ ;";" ;5;5 )*% )*%7 -./ ;" ;" ;5 ;5 )*% )*%7 -./ ;" ;" ;5 ;5 )*% )*%7 -./ ;";" ;5;5 )*% )*%7 user?s manual 25 switchchar.c ?this program transmits and then receives an ascii string on serial ports e and f. it also displays the serial data received from both ports in the stdio window. to set up the prototyping board, you will need to tie txe and rxf together on the rs-232 header at j14, and you will also tie rxe and txf together as shown in the diagram. once you have compiled and run this program, press and release s2 on the prototyping board to send a message from serial port e to serial port f; press and release s3 on the protot yping board to send a message from serial port f to serial port e. the data sent betw een the serial ports will be displayed in the stdio window. two sample programs, simple485master.c and simple485slave.c , are available to illustrate rs-485 master/slave communica tion. to run these sample programs, you will need a second rabbit-based system with rs-485?the second system may be another rcm3365/RCM3375, or it may be any rabbit si ngle-board computer or rabbitcore mod- ule that supports rs-485 serial communication as long as you use the master or slave sam- ple program associated with that board. before running either of these sample programs on the rcm3365/RCM3375 assembly, make sure pins 1?2 and pins 5?6 are jumpered together on header jp5 to use the rs-485 bias and termination resistors. the sample pr ograms use serial port c as the rs-485 serial port, and they use pd7 to enable/disable the rs-485 transmitter. the rs-485 connections between the slav e and master devices are as follows. ? rs485+ to rs485+ ? rs485? to rs485? ? gnd to gnd simple485master.c ?this program demonstrates a simple rs-485 transmission of lower case letters to a slave. the slave will send back converted upper case letters back to the master and display them in the stdio window. use simple485slave.c to program the slave?reset the slave before you run simple485master.c on the master. simple485slave.c ?this program demonstrates a simple rs-485 transmission of lower case letters to a master. the slave will send back converted upper case letters back to the master and display them in the stdio window. compile and run this pro- gram on the slave before you use simple485master.c to program the master. 3.2.4 real-time clock if you plan to use the real-time clock functiona lity in your applicati on, you will need to set the real-time clock. set the real-time clock using the setrtckb.c sample program from the dynamic c samples\rtclock folder, using the onscreen prompts. the rtc_ test.c sample program in the dynamic c samples\rtclock folder provides addi- tional examples of how to read and set the real-time clock. -./ ;" ;" ;5 ;5 )*% )*%7 26 rabbitcore rcm3365/RCM3375 3.2.5 rabbitnet sample programs are available for each rabb itnet peripheral card, and can be found in the dynamic c samples\rabbitnet folder. when you run any of these sample programs in conjunction with the rcm3365/RCM3375 and the prototyping board, you need to add the line #use rcm33xx.lib at the beginning of the sample program. tip: you need to add #use rcm33xx.lib at the beginning of any sample program that is not in the dynamic c samples\rcm3360 folder. 3.2.6 other sample programs section 6.6 describes the tcp/ip sample programs, and appendix c.7 provides sample programs for the optional lcd/keypad module that can be installed on the prototyping board. user?s manual 27 4. h ardware r eference chapter 4 describes the hardware components and principal hardware subsystems of the rcm3365/RCM3375 modules. appendix a, ?rcm3365/RCM3375 specifications,? provides complete physical and electrical specifications. figure 5 shows the rabbit-based subsystems designed into the rcm3365/RCM3375. figure 5. rcm3365/RCM3375 subsystems $ % $, 0 &111 2 &3 %4 !" # " $ % " #& ' $ !# ( ) (( # " ## * !( ! # +% "% # #& "# ,- . / & / # - 0( . 1 # - 22 / & 28 rabbitcore rcm3365/RCM3375 4.1 rcm3365/RCM3375 inputs and outputs figure 6 shows the rcm3365/RCM3375 pinouts for headers j3 and j4. figure 6. rcm3365/RCM3375 pinouts the pinouts for the rcm3000, rcm3100, rcm3200, rcm3300/rcm3310, rcm3360/ rcm3370, and rcm3365/RCM3375 are almost compatible, except signals pb0, pc4, and pc5. pb0, pc4, and pc5 are used for the spi interface to the serial flash on the rcm3300 and the rcm3310, but are available on the other modules. pb0 on the rcm3365 and the RCM3375 is used to sense whether the removable xd-picture card card is installed. if you need pb0 for other purposes, you may remove the surface-mount resistor at r96 (figure a-5 shows the location of r96). headers j3 and j4 are standard 2 34 headers with a no minal 2 mm pitch. an rj-45 ether- net port is also included with the rcm3365/RCM3375. pins 29?32 on header j3 are configured using 0 ? resistors at locations jp4, jp5, jp7, and jp7 to be pd3, pd2, pd7, and pd6 respectively. they may also be reconfigured to carry the ethernet signals tpo+, tpo?, tpi+, and tpi?. pins 33 and 34 on header j3 are wired to carry the link and act signals that illuminated the corresponding leds on the rcm3365/RCM3375 module. these signals may be ?dis- connected? by removing 0 ? surface-mount resistors r41 and r42 (figure a-5 shows the locations of r41 and r42) . "! & ) + 5) 5+ "( "% "$ "' + ) !/"# 1/ $2$1 22 ' b $ % ( 5% 5( "+ ") "# ( % : !/"' "!" < 1 <"9 ! 4! + ) & ' 5& 5' # $ % (8; # $ % $ ( 22 ( % $ # 5$ 5# ' & ) +8 ; ' & ) & 7 + 7 22 5 6 b ' =a = 22c = user?s manual 29 figure 7 shows the use of the rabbit 3000 microprocessor ports in the rcm3365/ RCM3375 modules. figure 7. use of rabbit 3000 ports the ports on the rabbit 3000 microprocessor used in the rcm3365/RCM3375 are config- urable, and so the factory defaults can be reconfigured. table 2 lists the rabbit 3000 fac- tory defaults and the alternate configurations. $ , 0 &111 # # # '7( &7( "'7"#d "$7"( &7( "! : 3 #&$. 44 !' % # - !( ## * !(( # / & # 0 # 51 . ". # 0 #1 #& "# # )" > #d +d! 4! (d "!" d !/"'d!/"# 'd &d ) #d $d % #6 0 #5/1 #/ 5'75( "! &7$ +7( - ,78 '7#d )7% #6 0 #1 # 0 #& "# #1 30 rabbitcore rcm3365/RCM3375 table 2. rcm3365/RCM3375 pinout configurations pin pin name default use alternate use notes header j3 1gnd 2 status output (status) output 3?10 pa[7:0] parallel i/o external data bus (id0?id7) slave port data bus (sd0?sd7) external data bus 11 pf3 input/output qd2a 12 pf2 input/output qd2b 13 pf1 input/output qd1a clkc 14 pf0 input/output qd1b clkd 15 pc0 output txd serial port d 16 pc1 input rxd 17 pc2 output txc serial port c 18 pc3 input rxc 19 pc4 output txb serial port b 20 pc5 input rxb 21 pc6 output txa serial port a (programming port) 22 pc7 input rxa 23 pg0 input/output tclkf serial clock f output 24 pg1 input/output rclkf serial clock f input 25 pg2 input/output txf serial port f 26 pg3 input/output rxf 27 pd4 input/output atxb 28 pd5 input/output arxb 29 pd2/tpo? input/output tpout? * optional ethernet transmit port 30 pd3/tpo+ input/output tpout+ * 31 pd6/tpi? input/output tpin? * optional ethernet receive port 32 pd7/tpi+ input/output tpin+ * 33 link output max. sinking current draw 1 ma (see note 1) 34 act output * pins 29?32 are configured with 0 ? surface-mount resistors at jp4, jp5, jp7, and jp8. user?s manual 31 header j4 1 /res reset output reset output from reset generator 2 pb0 input/output clkb used to detect presence of xd-picture card 3 pb2 input/output ia0 /swr external address 0 slave port write 4 pb3 input/output ia1 /srd external address 1 slave port read 5 pb4 input/output ia2 sa0 external address 2 slave port address 0 6 pb5 input/output ia3 sa1 external address 3 slave port address 1 7 pb6 input/output ia4 external address 4 8 pb7 input/output ia5 /slaveattn external address 5 slave attention 9 pf4 input/output aqd1b pwm0 10 pf5 input/output aqd1a pwm1 11 pf6 input/output aqd2b pwm2 12 pf7 input/output aqd2a pwm3 13 pe7 input/output i7 /scs i/o strobe 7 slave port chip select 14 pe6 input/output i6 i/o strobe 6 15 pe5 input/output i5 int1b i/o strobe 5 interrupt 1b 16 pe4 input/output i4 int0b i/o strobe 4 interrupt 0b 17 pe3 input/output i3 i/o strobe 3 18 pe1 input/output i1 int1a i/o strobe 1 interrupt 1a 19 pe0 input/output i0 int0a i/o strobe 0 interrupt 0a table 2. rcm3365/RCM3375 pinout configurations (continued) pin pin name default use alternate use notes 32 rabbitcore rcm3365/RCM3375 notes 1. when using pins 33?34 on header j3 to drive leds, these pins can handle a sinking current of up to 8 ma. 2. the vram voltage is temperature-depende nt. if the vram voltage drops below about 1.2 v to 1.5 v, the contents of the battery-backed sram may be lost. if vram drops below 1.0 v, the 32 khz oscillator could stop running. pay careful attention to this volt- age if you draw any current from this pin. 3. do not overload the /iowr line because the nand flash memories have critical timing requirements. in some cases it may be necessary to buffer /iowr on the motherboard. header j4 20 pg7 input/output rxe serial port e 21 pg6 input/output txe 22 pg5 input/output rclke serial clock e input 23 pg4 input/output tclke serial clock e ouput 24 /iowr output external write strobe 25 /iord output external read strobe 26?27 smode0, smode1 (0,0)?start executing at address zero (0,1)?cold boot from slave port (1,0)?cold boot from clocked serial port a smode0 =1, smode1 = 1 cold boot from asynchronous serial port a at 2400 bps (programming cable connected) also connected to programming cable 28 /reset_in input input to reset generator 29 vram output see notes below table 30 vbat_ext 3 v battery input minimum battery voltage 2.85 v 31 +3.3 vin power input 3.15?3.45 v dc 32 gnd 33 n.c. reserved for future use 34 gnd table 2. rcm3365/RCM3375 pinout configurations (continued) pin pin name default use alternate use notes user?s manual 33 4.1.1 memory i/o interface the rabbit 3000 address lines (a0?a18) and al l the data lines (d0?d7) are routed internally to the onboard flash memory and sram chips. i/0 write (/iowr) and i/0 read (/iord) are available for interfacing to exte rnal devices?pay attention to the loading on these two signals if you use them since these signals are also used by the rcm3365/ RCM3375. parallel port a can also be used as an external i/o data bus to isolate external i/o from the main data bus. parallel port b pins pb2?pb7 ca n also be used as an auxiliary address bus. when using the external i/o bus for a di gital output or the lcd/keypad module on the prototyping board, or for any other reason, you must add the following line at the begin- ning of your program. #define porta_aux_io // required to enable external i/o bus 4.1.2 other inputs and outputs the status, /reset_in, smode0, and smode1 i/o are normally associated with the programming port. since the status pin is not used by the system once a program has been downloaded and is running, the status pin can then be used as a general-purpose cmos output. the programming port is descri bed in more detail in section 4.2.3. /res is an output from the reset circuitry th at can be used to reset external peripheral devices. 4.1.3 leds the rcm3365/RCM3375 has five status leds located beside the rj-45 ethernet jack: act , link , speed , fm , and usr . the yellow act led at ds1 indicates network activity. the green link led at ds2 indicates that the rcm3365/RCM3375 is connected to a working network. the green speed led at ds4 is on to indicate when the rcm3365/RCM3375 is con- nected to a 100base-t ethernet connection. the fm led at ds3 blinks when data are being written to or read from the flash mass- storage device. the red usr led at ds3 is a user-programmabl e led, which is controlled by pd0 on the rabbit 3000?s parallel port d. the sample program flashled.c provided in the dynamic c samples\rcm3360 folder shows how to set up and use this user- programmable led. 34 rabbitcore rcm3365/RCM3375 4.2 serial communication the rcm3365/RCM3375 does not have any serial transceivers directly on the board. however, a serial interface may be incorporated into the board the rcm3365/RCM3375 is mounted on. for example, the prototyping board has rs-232 and rs-485 transceiver chips. 4.2.1 serial ports there are six serial ports designated as serial ports a, b, c, d, e, and f. all six serial ports can operate in an asynchronous mode up to the baud rate of the system clock divided by 8. an asynchronous port can handle 7 or 8 da ta bits. a 9th bit a ddress scheme, where an additional bit is sent to mark the first byte of a message, is also supported. serial port a is normally used as a programming port, but may be used either as an asyn- chronous or as a clocked serial port onc e the rcm3365/RCM3375 has been programmed and is operating in the run mode. serial port b is available on the rcm3365/RCM3375, and may be used as an asynchronous port. pb0 is used to enable dynamic c to detect whether the xd-picture card is installed. if the card detect is not needed by your application program, you may remove r96 (see figure a-5) to disable the xd-picture card detect, and then use serial port b as a clocked serial port. serial ports c and d can also be operated in th e clocked serial mode. in this mode, a clock line synchronously clocks the data in or out. either of the two communicating devices can supply the clock. serial ports e and f can also be configured as hdlc serial ports. the irda protocol is also supported in sdlc format by these two ports. 4.2.2 ethernet port figure 8 shows the pinout for the rj-45 ethernet port (j2). note that some ethernet connectors are numbered in reve rse to the order used here. figure 8. rj-45 ethernet port pinout three leds are placed next to the rj-45 ethernet jack, one to indicate an ethernet link ( link ) one to indicate ethernet activity ( act ), and one to indicate the 10/100base-t speed. the rj-45 connector is shielded to minimize emi effects to/from the ethernet signals. $- /( #2"< ; &2"< ;7 $2"<; +2"<;7 # * $- /(-7 user?s manual 35 4.2.3 serial programming port the rcm3365/RCM3375 is programmed either through the serial programming port, which is accessed using header j1 or thr ough the ethernet jack. the rabbitlink may be used to provide a serial connection via th e rabbitlink?s ethernet jack. the programming port uses the rabbit 3000?s serial port a for communication; serial port a is not used when programming is done over an ethernet connection on a board running dynamic c rabbitsys. dynamic c uses the program ming port to download and debug programs. the programming port is also used for the following operations. cold-boot the rabbit 3000 on the rcm3365/RCM3375 after a reset. remotely download and debug a program ove r an ethernet connection using the rabbitlink eg2110. fast copy designated portions of flash me mory from one rabbit-based board (the master) to another (the slave) using the rabbit cloning board. in addition to serial port a, the rabb it 3000 startup-mode (smode0, smode1), status, and reset pins are available on the programming port. the two startup mode pins determine what happens after a reset?the rabbit 3000 is either cold-booted or the program begins executing at address 0x0000. the status pin is used by dynamic c to determine whether a rabbit microprocessor is present. the status output has three different programmable functions: 1. it can be driven low on the first op code fetch cycle. 2. it can be driven low during an interrupt acknowledge cycle. 3. it can also serve as a general-purpose cmos output. the /reset_in pin is an external input that is used to reset the rabbit 3000 and the rcm3365/RCM3375 onboard peripheral circuits . the serial programming port can be used to force a hard reset on the rcm3365/RCM3375 by asserting the /reset_in signal. no equivalent functionality exists for pr ogramming over an ethernet connection on a board running dynamic c rabbitsys. alternate uses of the serial programming port all three clocked serial port a signals are available as a synchronous serial port an asynchronous serial port, with the clock line usable as a general cmos i/o pin the programming port may also be used as a serial port once the application is running. the smode pins may then be used as inputs a nd the status pin may be used as an output. refer to the rabbit 3000 microprocessor user?s manual for more information. 36 rabbitcore rcm3365/RCM3375 4.3 serial programming cable the programming cable is used to connect the serial programming port of the rcm3365/ RCM3375 to a pc serial com port. the programming cable converts the rs-232 voltage levels used by the pc serial port to the cmos voltage levels used by the rabbit 3000. when the prog connector on the programming cable is connected to the rcm3365/ RCM3375 serial programming port at header j1, programs can be downloaded and debugged over the serial interface. the diag connector of the programming cable may be used on header j1 of the rcm3365/ RCM3375 with the rcm3365/RCM3375 operating in the run mode. this allows the pro- gramming port to be used as a regular serial port. 4.3.1 changing between program mode and run mode the rcm3365/RCM3375 is automatically in program mode when the prog connector on the programming cable is attached, and is automatically in run mode when no pro- gramming cable is attached. when the rabbit 3000 is reset, the operating mode is deter- mined by the state of the smode pins. when the programming cable?s prog connector is attached, the smode pins are pulled high, placing the rabbit 3000 in the program mode. when the programming cable?s prog connector is not attached, the smode pins are pulled low, causing the rabbit 3000 to operate in the run mode. figure 9. switching between program mode and run mode $!!, ! "# "$ "% & ' # $ % ( " )) &* &( )$ )+ $' &, )% -% )* )( !( " . # /# # & /& & # ".! . * #0 #0 1 "! "' "& ") "+ $ # ' & ) + #0 0#+ ' # & $ ) % + ( 0#% ' # & $ ! " . " '2%3$'1 0#( 4#& 4## )& )# &' #, )' $, !" 5 !6 /"/ 0( & ( $ ) % + , * 4+ #' + # # 0& 0# 0) 0+ $ & # '%1 %1 -& -#-# 0% 1/7/# 1/ 1/ 1/7 0$ & 0# $ 0& 1 "! !/' % ( "# ") "+ 5( 5% ( % $ ' 0* $2$1 1/ !/"# ) + "' "$ "% + ) & 5)5+"( /$$'' . !# "!" 0, !& !$ ( $ % $ # ( % $ # 5' 5& ' & ) + ! + & ) & ' + ) & ' 5# 5$ # $ % ( 0 0 !# # & * # ## 0$ #& , #& 0) 0#' # & #) % # #$ 4% #+ #% #( '' '# '& '$ ') '% '+ '( 4 4 ) #$ 4# 4& &,$ 681" &,$ 681" 4* &% &+ &( &* 0#) &) 4#' $* $( $% &+ 0% $+ &$ &# 4, && 0#$ $$ $) #( #* 49% 49# !&': 49& !&': 9& &% 0#& %' -+ ), ) % + ( &, $' $# $& " !& !$ !) !% !+ ;";" ;5;5)*% )*%7 -# -& -$ -) #+ &) &$ && &# "/4 " " 4) $2$1 %1 $2$1 %1 4$ 49) 9# 9#+ 9#( 9#$ 9#) 9#* 9#% 5'< 5'<- 0## ( 4( #* #, &' #) #% 9# 9& %% %+ %( %* +$ +) +% ++ %, +& %# %) ! &$8+ ! &$8+ +( +* +, (' !& $% $+ $( $* )$ !) 4#$ *# (* () # #) #% &+ &( #$ 4& #& ## 0# #' # + * #' ## #% #, &' &) &* $% (( (, (& (' (# *& $# %$ %) )) %* $) &' &# $+ &% &( &# #* #& #$ , 4$ ( & $ + .# , *) ) & % 4# % *' *% (' *+ +) (( %' &, 0, %, #') 4% +( )% #) 4+ 4) #* && 0+ 0( 0* 0) 0% && 0+ ) (, # )& *# *+ (+ 0& $' *& .& -& ,+ +( #'% !$ !# +# &$ 4#+ ) & ==> ? - 8 - 9:&"& ". ". $; ! " #$$%" #&$ '() "!" * + , ,- .) % )# % ". ## & ".( . ". ' , user?s manual 37 a program ?runs? in either mode, but can only be downloaded and debugged when the rcm3365/RCM3375 is in the program mode. refer to the rabbit 3000 microprocessor user?s manual for more information on the pro- gramming port. 4.3.2 standalone operation of the rcm3365/RCM3375 the rcm3365/RCM3375 must be programmed via the prototyping board or via a similar arrangement on a customer-supplied board. once the rcm3365/RCM3375 has been pro- grammed successfully, remove the serial programming cable from the programming con- nector and reset the rcm3365/RCM3375. the rcm3365/RCM3375 may be reset by cycling the power off/on or by pressing the reset button on the prototyping board. the rcm3365/RCM3375 module may now be removed from the prototyping board for end- use installation. caution: disconnect power to the prototyping board or other boards when removing or installing your rcm3365/RCM3375 module to protect against inadvertent shorts across the pins or damage to the rcm3365/RCM3375 if the pins are not plugged in correctly. do not reapply power until you have verified that the rcm3365/RCM3375 module is plugged in correctly. 38 rabbitcore rcm3365/RCM3375 4.4 memory 4.4.1 sram rcm3365/RCM3375 boards have 512k of program-execution fast sram at u11. the program-execution sram is not battery-backe d. there are 512k of battery-backed data sram installed at u10. 4.4.2 flash eprom rcm3365/RCM3375 boards also have 512k of flash eprom at u9. note: rabbit recommends that any customer applications should not be constrained by the sector size of the flash eprom since it may be necessary to change the sector size in the future. writing to arbitrary flash memory addresses at run time is also discouraged. instead, use a portion of the ?user block? area to store persistent da ta. the functions writeuser- block and readuserblock are provided for this. refer to the rabbit 3000 micropro- cessor designer?s handbook and the dynamic c function reference manual for additional information. 4.4.3 nand flash the rcm3365 and the RCM3375 support a removable xd-picture card? to store data and web pages. the rcm3365 and the RCM3375 both can handle up to a 128mb removable xd-picture card , and the rcm3365 model also has a 32mb onboard nand flash. * note: rabbit-based systems do not implement the xd-picture card ? specification for data storage, and are neither compatible nor compliant with xd-picture card ? card readers. the nand flash and xd-picture card are particularly suitable for mass-storage applica- tions, but are generally unsuitable for dire ct program execution. the nand flash differs from parallel nor flash (the type of flash me mory used to store program code on rabbit- based boards and rabbitcore modules currently in production) in two respects. first, the nand flash requires error-correcting code (ecc) for reliability. although nand flash manufacturers do guarantee that block 0 will be error-free, most manufacturers guarantee that a new nand flash chip will be shipped wi th a relatively small percentage of errors, and will not develop more than some maximu m number or percentage of errors over its rated lifetime of up to 100,000 writes. se cond, the standard nand flash addressing method multiplexes commands, da ta, and addresses on the same i/o pins, while requiring that certain control lines must be held stable for the duration of the nand flash access. the software function calls provided by rabbit for the nand flash take care of the data- integrity and reliability attributes. * rcm3365 modules sold before 2008 had 16mb fixed nand flash memory. user?s manual 39 figure 10 shows how to insert or remove the xd-picture card . while you remove or insert the xd-picture card , take care to avoid touching the elec trical contacts on the bottom of the card to prevent electrostatic discharge damage to the card and to keep any moisture or other contaminants off the contacts. do not remove or insert the xd-picture card while it is being accessed. figure 10. insertion/removal of xd-picture card it is possible to hot-swap xd-picture cards without removing power from the rcm3365/ RCM3375 module. the file system must be cl osed before the cards can be hot-swapped. the chip selects associated with the nand flash and the xd-picture card must be set to their inactive state, and read/write operati ons addressed to the nand flash area cannot be allowed to occur. these operations can be initiated in software by sensing an external switch actuated by the user, and the xd-picture card can then be removed and replaced with a different one. once the application progr am detects a new card, the file system can be opened. these steps allow the xd-picture card to be installed or removed without affecting either the program, which con tinues to run on the rcm3365/RCM3375 module, or the data stored on the xd-picture card . the fat_hot_swap_336x0.c sample program in the samples\filesystem\ folder illustrates this hot-swapping procedure. rabbit recommends that you use header j6 only for the xd-picture card since other devices are not supported. be care ful to remove and insert the xd-picture card as shown, and be careful not to insert any foreign objects, which may short out the contacts and lead to the destruction of your xd-picture card . sample programs in the samples\rcm3360\nandflash folder illustrate the use of the nand flash. these sample programs are described in section 3.2.1, ?use of nand flash.? pay careful attention to the sample pr ograms to see how to close files and secure any data on the xd-picture card before you remove it. !& $% $+ $( $* )$ !) 4#$ *# (* () # #) #% &+ &( #$ 4& #& ## 0# #' # + * #' ## #% #, &' &) &* $% (( (, (& (' (# *& $# %$ %) )) %* $) &' &# $+ &% &( &# #* #& #$ , 4$ ( & $ + .# , *) ) & % 4# % *' *% (' *+ +) (( %' &, 0, %, #') 4% +( )% #) 4+ 4) #* && 0+ 0( 0* 0) 0% && 0+ ) (, # )& *# *+ (+ 0& $' *& .& -& ,+ +( #'% !$ !# +# &$ 4#+ ) & 40 rabbitcore rcm3365/RCM3375 4.5 other hardware 4.5.1 clock doubler the rcm3365/rcm33610 takes advantage of th e rabbit 3000 microprocessor?s internal clock doubler. a built-in clock doubler allows hal f-frequency crystals to be used to reduce radiated emissions. the 44.2 mhz frequency specified for the rcm3365/RCM3375 is generated using a 22.12 mhz resonator. the clock doubler may be disabled if 44.2 mh z clock speeds are not required. this will reduce power consumption and further reduce radiated emissions. the clock doubler is disabled with a simple confi guration macro as shown below. 4.5.2 spectrum spreader the rabbit 3000 features a spectrum spreader, which helps to mitigate emi problems. the spectrum spreader is on by default, but it may al so be turned off or set to a stronger setting. the means for doing so is through a simple configuration macro as shown below. note: refer to the rabbit 3000 microprocessor user?s manual for more information on the spectrum-spreading setting and the maximum clock speed. 1. select the ?defines? tab from the dynamic c options > project options menu. 2. add the line clock_doubled=0 to always disable the clock doubler. the clock doubler is enabled by default, and us ually no entry is needed. if you need to specify that the clock doubler is always enabled, add the line clock_doubled=1 to always enable the clock doubler. 3. click ok to save the macro. the clock doubler will now remain off whenever you are in the project file where you defined the macro. 1. select the ?defines? tab from the dynamic c options > project options menu. 2. normal spreading is the default, and usually no entry is needed. if you need to specify normal spreading, add the line enable_spreader=1 for strong spreading, add the line enable_spreader=2 to disable the spectrum spreader, add the line enable_spreader=0 note: the strong spectrum-spreading setting is not recommended since it may limit the maximum clock speed or the maximum baud rate. it is unlikely that the strong set- ting will be used in a real application. 3. click ok to save the macro. the spectrum spreader will now be set to the state specified by the macro value whenever you are in the project file where you defined the macro. user?s manual 41 5. s oftware r eference dynamic c is an integrated de velopment system for writing embedded software. it runs on an ibm-compatible pc and is designed for use with rabbit controllers and other controllers based on the rabbit microproces sor. chapter 5 describes the libraries and function calls related to the rcm3365/RCM3375. 5.1 more about dynamic c dynamic c has been in use wo rldwide since 1989. it is specially designed for program- ming embedded systems, and features quick compile and interactive debugging. a com- plete reference guide to dynamic c is contained in the dynamic c user?s manual . you have a choice of doing your software devel opment in the flash memory or in the static sram included on the rcm3365/RCM3375. the flash memory and sram options are selected with the options > program options > compiler menu. the advantage of working in ram is to save wear on the flash memory, which is limited to about 100,000 write cycles. the disadvantage is that the code and data might not both fit in ram. note: an application should be run from the program execution sram after the serial programming cable is disconnected. your final code must always be stored in flash memory for reliable operation. rcm3365/RCM3375 modules running at 44.2 mhz have a fast program execution sram that is not battery-backed. select code and bios in flash, run in ram from the dynamic c options > project options > compiler menu to store the code in flash and copy it to the fast program execution sram at run-time to take advantage of the faster clock speed. this option optimizes the performance of rcm3365/RCM3375 modules running at 44.2 mhz. note: do not depend on the flash memory sector size or type in your program logic. the rcm3365/RCM3375 and dynamic c were designed to accommodate flash devices with various sector sizes in response to the volatility of the flash-memory market. developing software with dynamic c is simple . users can write, compile, and test c and assembly code without leaving the dyna mic c development environment. debugging occurs while the application runs on the target . alternatively, users can compile a program to an image file for later loading. d ynamic c runs on pcs under windows 2000/nt and later?see rabbit?s technical note tn257, running dynamic c ? with windows vista ? , 42 rabbitcore rcm3365/RCM3375 for additional information if you are using a dynamic c release prior to v. 9.60 under win- dows vista. programs can be downloaded at baud rates of up to 460,800 bps after the pro- gram compiles. dynamic c has a number of standard features. full-feature source and/or assembly-level debugger, no in-circuit emulator required. royalty-free tcp/ip stack with sour ce code and most common protocols. hundreds of functions in source-c ode libraries and sample programs: x exceptionally fast support for floating-point arithmetic and transcendental functions. x rs-232 and rs-485 serial communication. x analog and digital i/o drivers. x i 2 c, spi, gps, file system. x lcd display and keypad drivers. powerful language extensions for c ooperative or preemptive multitasking loader utility program to load binary images into rabbit targets in the absence of dynamic c. provision for customers to create their own s ource code libraries and augment on-line help by creating ?function description? bloc k comments using a special format for library functions. standard debugging features: x breakpoints?set breakpoints that can disable interrupts. x single-stepping?step into or over functions at a source or machine code level, c/os-ii aware. x code disassembly?the disassembly window disp lays addresses, opcodes, mnemonics, and machine cycle times. switch between debugging at machine-code level and source-code level by simply opening or closing the disassembly window. x watch expressions?watch expressions are compiled when defined, so complex expressions including function calls may be placed into watch expressions. watch expressions can be updated with or without stopping program execution. x register window?all processor registers and flags are displayed. the contents of general registers may be modified in the window by the user. x stack window?shows the contents of the top of the stack. x hex memory dump?displays the contents of memory at any address. x stdio window? printf outputs to this window and keyboard input on the host pc can be detected for debugging purposes. printf output may also be sent to a serial port or file. user?s manual 43 5.1.1 developing programs remotely with dynamic c dynamic c is an integrated development environment that allows you to edit, compile, and debug your programs. dynamic c has th e ability to allow programming over the internet or local ethernet. this is accomplished in one of three ways. 1. rcm3365 rabbitcore modules that are prel oaded with dynamic c rabbitsys firm- ware can be used with dynamic c rabbitsys to be accessed via an ethernet connection for remote application updates, and for re mote monitoring and control. dynamic c rabbitsys requires dynamic c version 9.30 or later, and allows the rcm3365. the dynamic c rabbitsys user?s manual provides complete information on rabbitsys. 2. via the rabbit rabbitlink, which allows a rabbit-based target to have programs down- loaded to it and debugged with the same ease as exists when the target is connected directly to a pc. 3. dynamic c provides sample programs to illus trate the use of a download manager, but these sample programs are not intended for use with the nand flash on the rcm3365 and RCM3375 rabbitcore modules. the dlm_tcp.c and dlp_tcp.c sample pro- grams found in the dynamic c samples\down_load folder, are intended to be com- piled to the program flash memory (which is a parallel flash memory). custom applications based on these sample programs may use the nand flash for data storage. 44 rabbitcore rcm3365/RCM3375 5.2 dynamic c functions 5.2.1 digital i/o the rcm3365/RCM3375 was designed to interface with other systems, and so there are no drivers written specifically for the i/o. the general dynamic c read and write func- tions allow you to customize the parallel i/o to meet your specific needs. for example, use wrporti(peddr, &peddrshadow, 0x00); to set all the port e bits as inputs, or use wrporti(peddr, &peddrshadow, 0xff); to set all the port e bits as outputs. when using the external i/o bus on the rabbit 3000 chip, add the line #define porta_aux_io // required to enable external i/o bus to the beginning of any programs using the external i/o bus. the sample programs in the dynamic c samples/rcm3360 folder provide further examples. 5.2.2 sram use the rcm3365/RCM3375 have a battery-backed data sram and a program-execution sram. dynamic c provides the protected keyword to identify variables that are to be placed into the battery-backed sram. the co mpiler generates code that maintains two copies of each protected variable in the battery-backed sram. the compiler also generates a flag to indicate which copy of the protected variable is valid at the current time. this flag is also stored in the battery-backed sram. when a protected variable is updated, the ?inactive? copy is modified, and is made ? active? only when the update is 100% complete. this assures the integrity of the data in cas e a reset or a power failure occurs during the update process. at power-on the application program uses the active copy of the variable pointed to by its associated flag. the sample code below shows how a protected variable is defined and how its value can be restored. protected nf_device nandflash; int main() { ... _sysissoftreset(); // restore any protected variables the bbram keyword may also be used instead if there is a need to store a variable in bat- tery-backed sram without affecting the perf ormance of the application program. data integrity is not assured when a reset or power failu re occurs during the update process. additional information on bbram and protected variables is available in the dynamic c user?s manual . user?s manual 45 5.2.3 serial communication drivers library files included with dynamic c provide a full range of serial communications sup- port. the rs232.lib library provides a set of circular -buffer-based serial functions. the packet.lib library provides p acket-based serial functions where packets can be delimited by the 9th bit, by transmission gaps, or with user-defined special characters. both libraries provide blocking functions, which do not return until they are finished transmitting or receiving, and nonblocking functi ons, which must be called repeatedly until they are fin- ished, allowing other functions to be perfor med between calls. for more information, see the dynamic c function reference manual and technical note tn213, rabbit serial port software . 5.2.4 tcp/ip drivers the tcp/ip drivers are located in the lib\tcpip folder. complete information on these libraries and the tcp/ip functions is provided in the dynamic c tcp/ip user?s manual . 5.2.5 nand flash drivers the dynamic c nandflash\nflash.lib library is used to interface to nand flash memory devices on the rcm3365 and the RCM3375. the function calls were written spe- cifically to work with industry-standard fl ash devices with a 528-byte page program and 16896-byte block erase size. the nand flash f unction calls are designed to be closely cross-compatible with the newer serial flash function calls found in the sflash.lib library. these function calls use an nf_device structure as a handle for a specific nand flash device. this allows multiple nand flash devices to be used by an application. more information on these function calls is available in the dynamic c function refer- ence manual . the nand flash and the xd-picture card are ideally suited to store files with a directory structure. the dynamic c fat file system module provides support for a file system and for formatting the xd-picture card for use in a rabbit-based system. visit our web site at www.rabbit.com or contact your rabbit sales representa tive or authorized distributor for further information on the dynamic c fat fi le system and other dynamic c modules. the supporting documentation for the dynamic c fat file system and the sample programs in the samples\filesystem\ folder illustrate the use of the dynamic c fat file system. 46 rabbitcore rcm3365/RCM3375 5.2.6 prototyping board functions the functions described in this section are for use with the prototyping board features. the source code is in the dynamic c samples\rcm3300\rcm33xx.lib library if you need to modify it for your own board design. the rcm33xx.lib library is supported by the rn_cfg_rcm33.lib ?library, which is used to configure the rcm3365/RCM3375 for use with rabbitnet peripheral boards on the prototyping board. other generic functions applicable to all devices based on rabbit microprocessors are described in the dynamic c function reference manual . 5.2.6.1 board initialization call this function at the beginning of your program. this function initializes parallel ports a through g for use with the prototyping board. summary of initialization 1. i/o port pins are configured for prototyping board operation. 2. unused configurable i/o are set as tied inputs or outputs. 3. external i/o are disabled. 4. the lcd/keypad module is disabled. 5. rs-485 is not enabled. 6. rs-232 is not enabled. 7. leds are off. 8. ethernet select is disabled. 9. mass-storage flash select is disabled. 10. motor control is disabled. 11. the rabbitnet spi interface is disabled. 12. the relay is set to normally closed positions. return value none. void brdinit (void); user?s manual 47 5.2.6.2 digital i/o reads the input state of inputs on prototyping board headers j5 and j6. do not use this function if you configure these pins for alternate use after brdinit() is called. parameters channels is the channel number corresponding to the signal on header j5 or j6 0?in0 1?in1 2?in2 3?in3 4?qd1b 5?qd1a 6?qd2b 7?qd2a return value the logic state (0 or 1) of the input. see also brdinit writes a value to an output channel on prototyping board header j10. do not use this function if you have installed the stepper motor chips at u2 and u3. parameters channel is output channel 0?7 (out00?out07). value is the value (0 or 1) to output. return value none. see also brdinit int digin(int channel); void digout(int channel, int value); 48 rabbitcore rcm3365/RCM3375 5.2.6.3 switches, leds, and relay reads the state of a switch input. parameters swin is the switch input to read: 2?s2 3?s3 return value state of the switch input: 1 = open 0 = closed see also brdinit controls leds on the prototyping board and on the rcm3365/RCM3375. parameters led is the led to control: 0 = red user led on rcm3365/RCM3375 3 = ds3 on prototyping board 4 = ds4 on prototyping board 5 = ds5 on prototyping board 6 = ds6 on prototyping board value is the value used to control the led: 0 = off 1 = on return value none. see also brdinit int switchin(int swin); void ledout(int led, int value); user?s manual 49 sets the position for the relay common contact. the default position is for normally closed contacts. parameters relay is the one relay (1) value is the value used to connect the relay common contact: 0 = normally closed positions (nc1 and nc2) 1 = normally open positions (no1 and no2) return value none. see also brdinit 5.2.6.4 serial communication enables the rs-485 transmitter. transmitted data are echoed back into the receive data buffer. the echoed data may be used as an indicator for disabling the transmitter by using one of the following meth- ods: byte mode?disable the transmitter after the same byte that is transmitted is detected in the receive data buffer. block data mode?disable the transmitter after the same number of bytes transmitted are detected in the receive data buffer. remember to call the serxopen() function before running this function. see also ser485rx disables the rs-485 transmitter. this puts the device into the listen mode, which allows it to receive data from the rs-485 interface. remember to call the serxopen() function before running this function. see also ser485tx void relayout(int relay, int value); void ser485tx(void); void ser485rx(void); 50 rabbitcore rcm3365/RCM3375 5.2.6.5 rabbitnet port the function calls described in this section ar e used to configure the rabbitnet port on the prototyping board for use with rabbitnet peri pheral cards. the user?s manual for the spe- cific peripheral card you are using contains a dditional function calls related to the rabbit- net protocol and the individual periphe ral card. appendix f provides additional information about the rabbitnet. these rabbitnet peripheral cards are available at the present time. before using the rabbitnet port, add the following lines at the start of your program. #define rn_max_dev 10 // max number of devices #define rn_max_data 16 // max number of data bytes in any transaction #define rn_max_port 2 // max number of serial ports set the following bits in rnstatusabort to abort transmitting data after the status byte is returned. this does not affect the status byte and still can be interpreted. set any bit com- bination to abort: bit 7?device busy is hard-coded into driver bit 5?identifies router or slave bits 4,3,2?peripheral-board-specific bits bit 1?command rejected bit 0?watchdog timeout #define rnstatusabort 0x80 // hard-coded driver default to abort if the peripheral board is busy provides rn_init() with the serial port control information needed for rcm3365/RCM3375 modules . return value none. digital i/o card (rn1100) a/d converter card (rn1200) d/a converter card (rn1300) relay card (rn1400) keypad/display interface (rn1600) void rn_sp_info(); user?s manual 51 deactivates the rcm3365/RCM3375 rabbitnet port as a clocked serial port. this call is also used by rn_init() . parameters portnum = 0 return value none this is a macro that enables or asserts the rcm3365/ RCM3375 rabbitnet port chip select prior to data transfer. parameters portnum = 0 return value none this is a macro that disables or deasserts the rc m3365/RCM3375 rabbitnet port chip select to invali- date data transfer. parameters portnum = 0 return value none. void rn_sp_close(int port); void rn_sp_enable(int portnum); void rn_sp_disable(int portnum); 52 rabbitcore rcm3365/RCM3375 5.3 upgrading dynamic c dynamic c patches that focus on bug fixes are available from time to time. check the web site www.rabbit.com/support/ for the latest patches, workarounds, and bug fixes. 5.3.1 extras dynamic c installations are designed for use with the board they are included with, and are included at no charge as part of our low-cost kits. starting with dynamic c version 9.60, dynamic c includes the popular c/os-ii real- time operating system, point-to-point protoc ol (ppp), fat file system, rabbitweb, and other select libraries. rabbit also offers for purchase the rabbit embedded security pack featuring the secure sockets layer (ssl) and a specific advanced encryption standard (aes) library. in addition to the web-based technical s upport included at no extra charge, a one-year telephone-based technical support subscrip tion is also available for purchase. visit our web site at www.rabbit.com for further information and complete documentation. user?s manual 53 6. u sing the tcp/ip f eatures 6.1 tcp/ip connections programming and development can be done with the rcm3365/RCM3375 modules with- out connecting the ethernet port to a networ k. however, if you will be running the sample programs that use the ethernet capability or will be doing ethernet-enabled development, you should connect the rcm3365/RCM3375 module?s ethernet port at this time. before proceeding you will need to have the following items. if you don?t have ethernet access, you will need at least a 10base-t ethernet card (available from your favorite comput er supplier) installed in a pc. two rj-45 straight-through ethernet cables and a hub, or an rj-45 crossover ethernet cable. a straight-through and a crossover ethernet cable are included in the rcm3365/RCM3375 development kit. figure 11 shows how to identify the two cables based on the wires in the transparent rj-45 connectors. figure 11. how to identify straight-through and crossover ethernet cables ethernet cables and a 10base-t ethernet hub are available from rabbit in a tcp/ip tool kit. more information is available at www.rabbit.com . " ,"" ! = ee = 54 rabbitcore rcm3365/RCM3375 now you should be able to make your connections. 1. connect the ac adapter and the serial pr ogramming cable as shown in chapter 2, ?get- ting started.? 2. ethernet connections there are four options for connecting the rcm3365/RCM3375 module to a network for development and runtime purposes. the first two options permit total freedom of action in selecting network addresses and us e of the ?network,? as no action can inter- fere with other users. we recommend one of these options for initial development. no lan ? the simplest alternative for desktop development. connect the rcm3365/RCM3375 module?s ethernet port directly to the pc?s network interface card using an rj-45 crossover cable . a crossover cable is a special cable that flips some connections between the two connectors and permits direct connection of two cli- ent systems. a standard rj-45 network cable will not work for this purpose. micro-lan ? another simple alternative for desk top development. use a small eth- ernet 10base-t hub and connect both the pc?s network interface card and the rcm3365/RCM3375 module?s ethernet port to it using standard network cables. the following options require more care in address selection and testing actions, as conflicts with other users, servers and systems can occur: lan ? connect the rcm3365/RCM3375 module?s ethernet port to an existing lan, preferably one to which the developmen t pc is already connected. you will need to obtain ip addressing information from your network administrator. wan ? the rcm3365/RCM3375 is capable of direct connection to the internet and other wide area networks, but exceptional care should be used with ip address settings and all network-re lated programming and development. we recommend that development and debugging be done on a local network before connecting a rabbit- core system to the internet. tip: checking and debugging the initial setup on a micro-lan is recommended before connecting the system to a lan or wan. the pc running dynamic c does not need to be the pc with the ethernet card. 3. apply power plug in the ac adapter. the rcm3365/RCM3375 module and prototyping board are now ready to be used. user?s manual 55 6.2 tcp/ip primer on ip addresses obtaining ip addresses to interact over an existing, operating, network can involve a num- ber of complications, and must usually be done with cooperation from your isp and/or network systems administrator. for this reason, it is suggested that the user begin instead by using a direct connection between a pc and the rcm3365/RCM3375 using an ether- net crossover cable or a simple arrangement with a hub. (a crossover cable should not be confused with regular straight through cables.) in order to set up this direct connection, the user will have to use a pc without networking, or disconnect a pc from the corporate network, or install a second ethernet adapter and set up a separate private network attached to th e second ethernet adapter. disconnecting your pc from the corporate network may be easy or nearly impossible, depending on how it is set up. if your pc boots from the network or is dependent on the network for some or all of its disks, then it probably should not be di sconnected. if a second ethernet adapter is used, be aware that windows tcp/ip will send messages to one adapter or the other, depending on the ip address and the binding or der in microsoft products. thus you should have different ranges of ip addresses on your private network from those used on the cor- porate network. if both networks service the same ip address, th en windows may send a packet intended for your private network to th e corporate network. a similar situation will take place if you use a dial-up line to send a packet to the internet. windows may try to send it via the local ethernet network if it is also valid for that network. the following ip addresses are set aside for local networks and are not allowed on the internet: 10.0.0.0 to 10.255.255.255, 172.16.0.0 to 172.31.255.255, and 192.168.0.0 to 192.168.255.255. the rcm3365/RCM3375 uses a 10/100base-t type of ethernet connection, which is the most common scheme. the rj-45 connectors ar e similar to u.s. style telephone connec- tors, except they are larger and have 8 contacts. an alternative to the direct connection using a crossover cable is a direct connection using a hub. the hub relays packets received on any port to all of the ports on the hub. hubs are low in cost and are readily available. the rcm3365/RCM3375 uses 10/100 mbps ethernet, so the hub or ethernet adapter can be a 10 mbps unit, a 100 mbps unit, or a 10/100 mbps unit. in a corporate setting where the internet is br ought in via a high-speed line, there are typi- cally machines between the outside internet and the internal network. these machines include a combination of proxy servers and firewa lls that filter and multiplex internet traf- fic. in the configuration below, the rc m3365/RCM3375 could be given a fixed address so any of the computers on the local network w ould be able to contact it. it may be possi- ble to configure the firewall or proxy server to allow hosts on the internet to directly con- tact the controller, but it would probably be easier to place the controller directly on the external network outside of the firewall. this avoids some of the configuration complica- tions by sacrificing some security. 56 rabbitcore rcm3365/RCM3375 if your system administrator can give you an et hernet cable along with its ip address, the netmask and the gateway address, then you may be able to run the sample programs with- out having to setup a direct connection between your computer and the rcm3365/ RCM3375. you will also need the ip address of the nameserver, the name or ip address of your mail server, and your domain name for some of the sample programs. hub(s) firewall proxy server t1 in adapter ethernet ethernet network rcm3365/RCM3375 system typical corporate network user?s manual 57 6.2.1 ip addresses explained ip (internet protocol) addresses are expresse d as 4 decimal numbers separated by periods, for example: 216.103.126.155 10.1.1.6 each decimal number must be between 0 and 255. the total ip address is a 32-bit number consisting of the 4 bytes expressed as shown above. a local network uses a group of adja- cent ip addresses. there are always 2 n ip addresses in a local network. the netmask (also called subnet mask) determines how many ip addresses belong to the local network. the netmask is also a 32-bit address expressed in the same form as the ip address. an example netmask is: 255.255.255.0 this netmask has 8 zero bits in the least significant portion, and this means that 2 8 addresses are a part of the local netw ork. applied to the ip address above (216.103.126.155), this netmask would indicate that the following ip addresses belong to the local network: 216.103.126.0 216.103.126.1 216.103.126.2 etc. 216.103.126.254 216.103.126.255 the lowest and highest address are reserved for special purposes. the lowest address (216.102.126.0) is used to identify the local network. the highest address (216.102.126.255) is used as a broadcast address. us ually one other address is used for the address of the gateway out of the networ k. this leaves 256 - 3 = 253 available ip addresses for the example given. 58 rabbitcore rcm3365/RCM3375 6.2.2 how ip addresses are used the actual hardware connection via an ethern et uses ethernet adapter addresses (also called mac addresses). these are 48-bit a ddresses and are unique for every ethernet adapter manufactured. in order to send a packet to another computer, given the ip address of the other computer, it is first determined if the packet needs to be sent directly to the other computer or to the gateway. in either case, there is an ethernet address on the local network to which the packet must be sent. a table is maintained to allow the protocol driver to determine the mac address correspondi ng to a particular ip address. if the table is empty, the mac address is determined by se nding an ethernet broadcast packet to all devices on the local network asking the device with the desired ip address to answer with its mac address. in this way, the table entry can be filled in. if no device answers, then the device is nonexistent or inoperative, and the packet cannot be sent. some ip address ranges are reserved for use on internal networks, and can be allocated freely as long as no two internal hosts have the same ip address. these internal ip addresses are not routed to the internet, and a ny internal hosts using one of these reserved ip addresses cannot communicate on the external internet without being connected to a host that has a valid internet ip address. the host would either translate the data, or it would act as a proxy. each rcm3365/RCM3375 rabbitcore module has its own unique mac address, which consists of the prefix 0090c2 followed by a code that is unique to each rcm3365/ RCM3375 module. for example, a mac address might be 0090c2c002c0. tip: you can always obtain the mac address on your board by running the sample pro- gram display_mac.c from the samples\tcpip folder. user?s manual 59 6.2.3 dynamically assigned internet addresses in many instances, devices on a network do not ha ve fixed ip addresses. this is the case when, for example, you are assigned an ip address dynamically by your dial-up internet service provider (isp) or when you have a de vice that provides your ip addresses using the dynamic host configuration protoc ol (dhcp). the rcm3365/RCM3375 modules can use such ip addresses to send and receive packets on the internet, but you must take into account that this ip address may only be valid for the duration of the call or for a period of time, and could be a private ip addre ss that is not directly accessible to others on the internet. these addresses can be used to perform some internet tasks such as sending e-mail or browsing the web, but it is more di fficult to participate in conversations that originate elsewhere on the internet. if you want to find out this dynamically assigned ip address, under windows 98 you can run the winipcfg program while you are connected and look at the interface used to connect to the internet. many networks use ip addresses that are assigned using dhcp. when your computer comes up, and periodically after that, it reque sts its networking information from a dhcp server. the dhcp server may try to give you the same address each time, but a fixed ip address is usually not guaranteed. if you are not concerned about accessing the rcm3365/RCM3375 from the internet, you can place the rcm3365/RCM3375 on the internal network using an ip address assigned either statically or through dhcp. 60 rabbitcore rcm3365/RCM3375 6.3 placing your device on the network in many corporate settings, users are isolated from the internet by a firewall and/or a proxy server. these devices attempt to secu re the company from unauthorized network traffic, and usually work by disallowing traffi c that did not originate from inside the net- work. if you want users on the internet to communicate with your rcm3365/RCM3375, you have several options. you can either place the rcm3365/RCM3375 directly on the internet with a real internet address or place it behind the firewall. if you place the rcm3365/RCM3375 behind the firewall, you need to configure the firewall to translate and forward packets from the internet to the rcm3365/RCM3375. user?s manual 61 6.4 running tcp/ip sample programs we have provided a number of sample programs demonstrating various uses of tcp/ip for networking embedded systems. these programs require you to connect your pc and the rcm3365/RCM3375 board together on the same network. this network can be a local pri- vate network (preferred for initial experimentation and debugging), or a connection via the internet. the sample programs described in this chapte r may also be run with a rabbitsys-enabled rcm3365 operating in the rabbitsys mode. there is no change to the instructions when you use the serial programming cable. when you use an ethernet cable, you may use cat 5/6 straight-through ethernet cables to connect the rcm3365 and your pc to a dhcp net- work. it is not necessary to use a crossover cable for a direct conne ction. use the tcp/ip parameters such as the ip address that you id entified with the rdiscover utility; if you are using an ethernet crossover cable to connect the rcm3365 directly to your pc, use the tcp/ip parameters that you set up according to the instructions in appendix e. user?s pc ethernet crossover cable direct connection (network of 2 computers) hub ethernet cables to additional network elements direct connection using a hub rcm3365/RCM3375 system rcm3365/RCM3375 system 62 rabbitcore rcm3365/RCM3375 6.4.1 how to set ip addresses in the sample programs with the introduction of dynamic c 7.30 we have taken steps to make it easier to run many of our sample programs. you will see a tcpconfig macro. this macro tells dynamic c to select your conf iguration from a list of defa ult configurations. you will have three choices when you encount er a sample program with the tcpconfig macro. 1. you can replace the tcpconfig macro with individual my_ip_address , my_net- mask , my_gateway , and my_nameserver macros in each program. 2. you can leave tcpconfig at the usual default of 1, which will set the ip configurations to 10.10.6.100 , the netmask to 255.255.255.0 , and the nameserver and gateway to 10.10.6.1 . if you would like to change the default values, for example, to use an ip address of 10.1.1.2 for the rcm3365/RCM3375 board, and 10.1.1.1 for your pc, you can edit the values in the section that di rectly follows the ?general configuration? comment in the tcp_config.lib library. you will find this library in the lib\tcpip directory. 3. you can create a custom_config.lib library and use a tcpconfig value greater than 100. instructions for doing this are at the beginning of the tcp_config.lib library in the lib\tcpip directory. there are some other ?standard? configurations for tcpconfig that let you select differ- ent features such as dhcp. their valu es are documented at the top of the tcp_con- fig.lib library in the lib\tcpip directory. more information is available in the dynamic c tcp/ip user?s manual . user?s manual 63 6.4.2 how to set up your computer for direct connect follow these instructions to set up your pc or notebook. check with your administrator if you are unable to change the settings as desc ribed here since you may need administrator privileges. the instructions are specifically for windows 2000, but the interface is similar for other versions of windows. tip: if you are using a pc that is already on a network, you will disconnect the pc from that network to run these sample programs. write down the existing settings before changing them to facilitate restoring them when you are finished with the sample pro- grams and reconnect your pc to the network. 1. go to the control panel ( start > settings > control panel ), and then double-click the network icon. 2. select the network interface card used for the ethernet interface you intend to use (e.g., tcp/ip xircom credit card network adapter ) and click on the ?properties? button. depending on which version of windows your pc is running, you may have to select the ?local area connection? first, and then click on the ?properties? button to bring up the ethernet interface dialog. then ?confi gure? your interface card for a ?10base-t half-duplex? or an ?auto-negotiati on? connection on the ?advanced? tab. note: your network interface card will likely have a different name. 3. now select the ip address tab, and check specify an ip address , or select tcp/ip and click on ?properties? to assign an ip address to your computer (this will disable ?obtain an ip address automatically?): ip address : 10.10.6.101 netmask : 255.255.255.0 default gateway : 10.10.6.1 4. click 64 rabbitcore rcm3365/RCM3375 6.5 run the pingme.c sample program connect the crossover cable from your computer?s ethernet port to the rcm3365/ RCM3375 board?s rj-45 ethernet connector . open this sample program from the samples\tcpip\icmp folder, compile the program, a nd start it running under dynamic c. the crossover cable is connected from your co mputer?s ethernet adapter to the rcm3365/ RCM3375 board?s rj-45 ethernet connector. when the program starts running, the green link light on the rcm3365/RCM3375 module should be on to indicate an ethernet con- nection is made. (note: if the lnk light does not light, you may not be using a crossover cable, or if you are using a hub with straight-through cables perhaps the power is off on the hub.) the next step is to ping the board from your pc. this can be done by bringing up the ms- dos window and running the pingme program: ping 10.10.6.101 or by start > run and typing the entry ping 10.10.6.101 notice that the yellow act light flashes on the rcm3365/RCM3375 module while the ping is taking place, and indicates the transfer of data. the ping routine will ping the board four times and write a summary message on the screen describing the operation. 6.6 running additional sample programs with direct connect the following sample programs are in the dynamic c samples\rcm3360\tcpip\ folder. browseled.c ?this program demonstrates a ba sic controller running a web page. two ?device leds? are created along with two buttons to toggle them. users can use their web browser to change the status of the lights. the ds3 and ds4 leds on the prototyping board will match those on the web page. as long as you have not modified the tcpconfig 1 macro in the sample program, enter the following server address in your web browser to bring up the web page served by the sample program. http://10.10.6.100. otherwise use the tcp/ip settings you entered in the tcp_config.lib library. mboxdemo.c ?the optional lcd/keypad module (see appendix c) must be plugged in to the prototyping board when using th is sample program. this program demon- strates sending e-mail messages that are then shown on the lcd/keypad module dis- play. the keypad is used to scroll through a menu to view the messages, flip to other messages, mark messages as read, and delete messages. when a new e-mail arrives, an led on the lcd/keypad module turns on, and then turns off once the message has been marked as read. a log of all e-mail ac tions is kept, and can be displayed in the web browser. all current e-mails can also be read with the web browser. user?s manual 65 pingled.c ?this program demonstrates icmp by pi nging a remote host. it will flash leds ds3 and ds4 on the prototyping board when a ping is sent and received. smtp.c ?this program demonstrates using the smtp library to send an e-mail when the s2 and s3 switches on the prototypi ng board are pressed. leds ds3 and ds4 on the prototyping board will light up when e-mail is being sent. 6.6.1 rabbitweb sample programs you will need to have the dynamic c rabbitw eb module installed before you run the sample programs described in this section. the following sample programs are in the dynamic c samples\rcm3360\tcpip\rabbitweb folder. blinkleds.c ?this program demonstrates a basic example to change the rate at which the ds3 and ds4 leds on the prototyping board blink. doormonitor.c ?the optional lcd/keypad module (see appendix c) must be plugged in to the prototyping board when using th is sample program. this program demon- strates adding and monitoring password s entered via the lcd/keypad module. sprinkler.c ?this program demonstrates how to schedule times for the relay and digital outputs in a 24-hour period. 6.7 where do i go from here? note: if you purchased your rcm3365/RCM3375 through a distributor or through a rabbit partner, contact the distributor or partner first for technical support. if there are any problems at this point: use the dynamic c help menu to get further assistance with dynamic c. check the rabbit technical bulletin board and forums at www.rabbit.com/support/bb/ and at www.rabbit.com/forums/ . use the technical support e-mail form at www.rabbit.com/support/ . if the sample programs ran fine, you are now ready to go on. additional sample programs are described in the dynamic c tcp/ip user?s manual . please refer to the dynamic c tcp/ip user?s manual to develop your own applications. an introduction to tcp/ip provides background information on tcp/ip, and is available on the cd and on our web site . 66 rabbitcore rcm3365/RCM3375 user?s manual 67 a ppendix a. rcm 3365/RCM3375 s pecifications appendix a provides the specifications for the rcm3365/ RCM3375, and describes the conformal coating. 68 rabbitcore rcm3365/RCM3375 a.1 electrical and mechanical characteristics figure a-1 shows the mechanical dimensions for the rcm3365/RCM3375. figure a-1. rcm3365/RCM3375 dimensions note: all measurements are in inches followed by millimeters enclosed in parentheses. all dimensions have a manufacturing tolerance of 0.01" (0.25 mm). 0+ 0# 0& !& !# !$ !) '2%% #) '2#'' = &2% '2'*( &2& '2&)% +2& '2*+ && 0$ 0) &2(&% +,2& #2*%' )(2' '2+,' #(2% '2)( ##2, #2*%' )(2' #2$&' $$2% #2$(% $)2, #2#&+ &*2+ '2#$) $2) " $ %&&'() $ %&&*( " 2 " + '2'+$ #2+ ," " " -' 8$ %&&'()$ %&&*( 9 1+../:8;+<9+ '2&' %2' '2#( )2$ '2,( &)2( user?s manual 69 it is recommended that you allow for an ?exclusion zone? of 0.04" (1 mm) around the rcm3365/RCM3375 in all directions when the rcm3365/RCM3375 is incorporated into an assembly that includes other printed ci rcuit boards. an ?exclusion zone? of 0.08" (2 mm) is recommended below the rcm3365/RCM3375 when the rcm3365/RCM3375 is plugged into another assembly. fi gure a-2 shows this ?exclusion zone.? figure a-2. rcm3365/RCM3375 ?exclusion zone? note: all measurements are in inches followed by millimeters enclosed in parentheses. '2'* & '2'* & 0$ 0) !2 = &2(&% +,2& #2*%' )(2' '2+ #+ '2+ #+ &2*# (#2& #2,$ ),2' 70 rabbitcore rcm3365/RCM3375 table a-1 lists the electrical, mechanical, and environmental specifications for the rcm3365/ RCM3375. table a-1. rabbitcore rcm3365/RCM3375 specifications parameter rcm3365 RCM3375 microprocessor low-emi rabbit ? 3000 at 44.2 mhz emi reduction spectrum spreader for reduced emi (radiated emissions) ethernet port 10/100base-t, rj-45, 3 leds sram 512k program (fast sram) + 512k data flash memory (program) 512k flash memory (mass data storage) 32mb (fixed) * + xd-picture card with up to 128mb (nand flash) xd-picture card with up to 128mb (nand flash) led indicators act (activity) link (link) speed (on for 100base-t ethernet connection) fm (flash memory, nand) usr (user-programmable) backup battery connection for user-supplied backup battery (to support rtc and data sram) general-purpose i/o 52 parallel digital i/0 lines: ? 44 configurable i/o ? 4 fixed inputs ? 4 fixed outputs additional inputs startup mode (2), reset in additional outputs status, reset out external i/o bus can be configured for 8 data lines and 5 address lines (shared with parallel i/o lines), plus i/o read/write serial ports six 3.3 v, cmos-compatible ports (shared with i/o) all 6 configurable as asynchronous (with irda) 4 configurable as clocked serial (spi) 2 configurable as sdlc/hdlc 1 asynchronous serial port dedicated for programming serial rate maximum asynchronous baud rate = clk/8 slave interface a slave port allows the rcm3365/RCM3375 to be used as an intelligent peripheral device slaved to a master processor, which may either be another rabbit 3000 or any other type of processor real-time clock yes timers ten 8-bit timers (6 cascadable, 3 reserved for internal peripherals), one 10-bit timer with 2 match registers user?s manual 71 note: m-type xd-picture cards are not supported at this time. watchdog/ supervisor yes pulse-width modulators 4 pwm registers with 10-bit free-running counter and priority interrupts input capture 2-channel input capture can be used to time input signals from various port pins quadrature decoder 2-channel quadrature decoder accepts inputs from external incremental encoder modules power 3.15?3.45 v dc 250 ma @ 44.2 mhz, 3.3 v operating temperature -40c to +70c (boards manufactured up to may, 2008) 0c to +70c (boards manufactured after may, 2008) humidity 5% to 95%, noncondensing connectors two 2 17, 2 mm pitch one 2 5 for programming with 1.27 mm pitch one xd-picture card slot (rcm3365/RCM3375) board size 1.850" 2.725" 0.86" (47 mm 69 mm 22 mm) * rcm3365 modules sold before 2008 had 16mb fixed nand flash memory. table a-1. rabbitcore rcm3365/RCM3375 specifications (continued) parameter rcm3365 RCM3375 72 rabbitcore rcm3365/RCM3375 a.1.1 headers the rcm3365/RCM3375 uses headers at j3 and j4 for physical connection to other boards. j3 and j4 are 2 17 smt headers w ith a 2 mm pin spacing. j1, the programming port, is a 2 5 header with a 1.27 mm pin spacing. figure a-3 shows the layout of another board for the rcm3365/RCM3375 to be plugged into. these reference design values are relative to the mounting hole. figure a-3. user board footprint for rcm3365/RCM3375 0# #2#&) &*2% #2$)# $)2# 0$ 0) /$$''! 5 ? '2'(, &2' '2#'' = &2% '2'&'f ? '2% '2'(, &2' '2$#) *2' #2#,* $'2) #2#$+ &*2, '2$&* *2$ '2,%$ &)2& #2#$% &*2* #2')$ &+2% '2'#' '2&% #2&'% $'2+ user?s manual 73 a.2 bus loading you must pay careful attention to bus loading when designing an interface to the rcm3365/RCM3375. this section provides bus loading information for external devices. table a-2 lists the capacitance for the various rcm3365/RCM3375 i/o ports. table a-3 lists the external capacitive bus loading for the various rcm3365/RCM3375 output ports. be sure to add the loads for the devices you are using in your custom system and verify that they do not exceed the values in table a-3. table a-2. capacitance of rabbit 3000 i/o ports i/o ports input capacitance (pf) output capacitance (pf) parallel ports a to g 12 14 table a-3. external capacitive bus loading -40c to +85c output port clock speed (mhz) maximum external capacitive loading (pf) all i/o lines with clock doubler enabled 44.2 100 74 rabbitcore rcm3365/RCM3375 figure a-4 shows a typical timing diagram for the rabbit 3000 microprocessor external i/o read and write cycles. figure a-4. i/o read and write cycles?no extra wait states note: /iocsx can be programmed to be active low (default) or active high. = = !2 )4$ 8 9 g#%h'i !2 )4> 8 9 g#%h'i # a # a & & 45" !; : 45" g(h'i @? = !; !; !; !; 45" !; !; 45" g(h'i !; !; !; : !; !; : 45" 45" 6j1 16j user?s manual 75 table a-4 lists the delays in gross memory access time at 3.3 v. the measurements are taken at the 50% points under the following conditions. t = -40c to 85c, v = v dd 10% internal clock to nonloaded clk pin delay 1 ns @ 85c/3.0 v the clock to address output delays are si milar, and apply to the following delays. t adr , the clock to address delay t csx , the clock to memory chip select delay t iocsx , the clock to i/o chip select delay t iord , the clock to i/o read strobe delay t iowr , the clock to i/o write strobe delay t bufen , the clock to i/o buffer enable delay the data setup time delays are similar for both t setup and t hold . when both the spectrum spreader and the clock doubler are enabled, every other clock cycle is shortened (sometime s lengthened) by a maximum amount given in the table above. the shortening takes plac e by shortening the high part of the clock. if the doubler is not enabled, then every clock is shortene d during the low part of the clock period. the maximum shortening for a pair of cloc ks combined is shown in the table. technical note tn227, interfacing external i/o with rabbit 2000/3000 designs , con- tains suggestions for interfacing i/o de vices to the rabbit 3000 microprocessors. table a-4. data and clock delays vin 10%, temp, -40c?+85c (maximum) vin clock to address output delay (ns) data setup time delay (ns) spectrum spreader delay (ns) 30 pf 60 pf 90 pf normal no dbl/dbl strong no dbl/dbl 3.3 v 6 8 11 1 3/4.5 4.5/9 76 rabbitcore rcm3365/RCM3375 a.3 rabbit 3000 dc characteristics stresses beyond those listed in table a-5 may cause permanent damage. the ratings are stress ratings only, and functional operation of the rabbit 3000 chip at these or any other conditions beyond those indicated in this secti on is not implied. exposure to the absolute maximum rating conditions for extended periods may affect the reliability of the rabbit 3000 chip. table a-6 outlines the dc characteristics for the rabbit 3000 at 3.3 v over the recom- mended operating temperature range from t a = ?55c to +85c, v dd = 3.0 v to 3.6 v. table a-5. rabbit 3000 absolute maximum ratings symbol parameter maximum rating t a operating temperature -55 to +85c t s storage temperature -65 to +150c maximum input voltage: oscillator buffer input 5-v-tolerant i/o v dd + 0.5 v 5.5 v v dd maximum operating voltage 3.6 v table a-6. 3.3 volt dc characteristics symbol parameter test conditions min typ max units v dd supply voltage 3.0 3.3 3.6 v v ih high-level input voltage 2.0 v v il low-level input voltage 0.8 v v oh high-level output voltage i oh = 6.8 ma, v dd = v dd (min) 0.7 x v dd v v ol low-level output voltage i ol = 6.8 ma, v dd = v dd (min) 0.4 v i ih high-level input current (absolute worst case, all buffers) v in = v dd , v dd = v dd (max) 10 a i il low-level input current (absolute worst case, all buffers) v in = v ss , v dd = v dd (max) -10 a i oz high-impedance state output current (absolute worst case, all buffers) v in = v dd or v ss , v dd = v dd (max), no pull-up -10 10 a user?s manual 77 a.4 i/o buffer sourcing and sinking limit unless otherwise specified, the rabbit i/o buf fers are capable of sourcing and sinking 6.8 ma of current per pin at full ac sw itching speed. full ac switching assumes a 22.1 mhz cpu clock and capacitive loading on a ddress and data lines of less than 100 pf per pin. the absolute maximum operating voltage on all i/o is 5.5 v. table a-7 shows the ac and dc output drive limits of the parallel i/o buffers when the rabbit 3000 is used in the rcm3365/RCM3375. under certain conditions, you can exceed the limits outlined in table a-7. see the rabbit 3000 microprocessor user?s manual for additional information. table a-7. i/o buffer sourcing and sinking capability pin name output drive (full ac switching) sourcing/sinking limits (ma) sourcing sinking all data, address, and i/o lines with clock doubler enabled 6.8 6.8 78 rabbitcore rcm3365/RCM3375 a.5 jumper configurations figure a-5 shows the jumper locations used to configure the various rcm3365/ RCM3375 options. the black square indicates pin 1. figure a-5. location of rcm3365/RCM3375 configurable positions )# )& 0$ 0+ 0( 0* 0) 0% $ %&&'()$ %&&*( , 0& ,+ 0, user?s manual 79 table a-8 lists the configuration options. note: the jumper connections are made using 0 ? surface-mounted resistors. table a-8. rcm3365/RCM3375 jumper configurations header description pins connected factory default jp2 flash memory bank select 1?2 bank mode 2?3 normal mode jp3 data sram size 1?2 128k/256k 2?3 512k jp4 ethernet or i/o output on header j3 1?2 tpo+ 2?3 pd3 jp5 ethernet or i/o output on header j3 1?2 tpo? 2?3 pd2 jp6 ethernet or i/o output on header j3 1?2 enet_int 2?3 pe0 jp7 ethernet or i/o output on header j3 1?2 tpi+ 2?3 pd7 jp8 ethernet or i/o output on header j3 1?2 tpi? 2?3 pd6 jp9 chip select signals for nand flash and xd-picture card 1?2 separate chip select signals to nand flash and xd-picture card 2?3 separate chip select signals for nand flash and xd-picture card r96 xd-picture card detect installed xd-picture card detect available not installed pb0 may be used as clkb (synchronous serial port b) 80 rabbitcore rcm3365/RCM3375 a.6 conformal coating the areas around the 32 khz real-time clock crystal oscillator have had the dow corning silicone-based 1-2620 conformal coating applied. the conforma lly coated area is shown in figure a-6. the conformal coating protects these high-impedance circuits from the effects of moisture and contaminants over time. figure a-6. rcm3365/RCM3375 areas receiving conformal coating any components in the conformally coated area may be replaced using standard soldering procedures for surface-mounted components. a new conformal coating should then be applied to offer continuing protection against the effects of moisture and contaminants. note: for more information on conformal coatings, refer to technical note 303, conformal coatings . !& $% $+ $( $* )$ !) 4#$ *# (* () # #) #% &+ &( #$ 4& #& ## 0# #' # + * #' ## #% #, &' &) &* $% (( (, (& (' (# *& $# %$ %) )) %* $) &' &# $+ &% &( &# #* #& #$ , 4$ ( & $ + .# , *) ) & % 4# % *' *% (' *+ +) (( %' &, 0, %, #') 4% +( )% #) 4+ 4) #* && 0+ 0( 0* 0) 0% && 0+ ) (, # )& *# *+ (+ 0& $' *& .& -& ,+ +( #'% !$ !# +# e = &$ 4#+ ) & user?s manual 81 a ppendix b. p rototyping b oard appendix b describes the features and accessories of the proto- typing board. 82 rabbitcore rcm3365/RCM3375 b.1 introduction the prototyping board included in the deve lopment kit makes it easy to connect an rcm3365/RCM3375 module to a power supply and a pc workstation for development. it also provides some basic i/o peripherals (r s-232, rs-485, a relay, leds, and switches), as well as a prototyping area for more advanced hardware development. for the most basic level of evaluation and development, the prototyping board can be used without modification. as you progress to more sophisticated exper imentation and hardware development, modi- fications and additions can be made to th e board without modifying or damaging the rcm3365/RCM3375 module itself. the prototyping board is shown below in figur e b-1, with its main features identified. figure b-1. prototyping board ! "# "$ "% & ' # $ % ( " )) &* &( )$ )+ $' &, )% -% )* )( !( " . # /# # & /& & # ".! . * #0 #0 1 "! "' "& ") "+ $ # ' & ) + #0 0#+ ' # & $ ) % + ( 0#% ' # & $ ! " . " '2%3$'1 0#( 4#& 4## )& )# &' #, )' $, !" 5 !6 /"/ 0( & ( $ ) % + , * 4+ #' + # # 0& 0# 0) 0+ $ & # '%1 %1 -&-#-# 0% 1/7/# 1/ 1/ 1/7 0$ & 0# $ 0& 1 "! !/' % ( "# ") "+ 5( 5% ( % $ ' 0* $2$1 1/ !/"# ) + "' "$ "% + ) & 5)5+"( /$$'' . !# "!" 0, !& !$ ( $ % $ # ( % $ # 5' 5& ' & ) + ! + & ) & ' + ) & ' 5# 5$ # $ % ( 0 0 !# # & * # ## 0$ #& , #& 0) 0#' # & #) % # #$ 4% #+ #% #( '' '# '& '$ ') '% '+ '( 4 4 ) #$ 4# 4& &,$ 681" &,$ 681" 4* &% &+ &( &* 0#) &) 4#' $* $( $% &+ 0% $+ &$ &# 4, && 0#$ $$ $) #( #* 49% 49# !&': 49& !&': 9& &% 0#& %' -+ ), ) % + ( &, $' $# $& " !& !$ !) !% !+ ;";" ;5;5)*% )*%7 -# -& -$ -) #+ &) &$ && &# "/4 " " 4) $2$1 %1 $2$1 %1 4$ 49) 9# 9#+ 9#( 9#$ 9#) 9#* 9#% 5'< 5'<- 0## ( 4( #* #, &' #) #% 9# 9& %% %+ %( %* +$ +) +% ++ %, +& %# %) ! &$8+ ! &$8+ +( +* +, (' 1 > >@ a ?@ a " !a 4 " / =@ "; 6= %1d$2$1d= @ /$$+' /$$(' / =@ !8&$& !> 4 !a !/ ?> ?= / =@ kk @> 86 ?> l " l l !8)*% 4 " l l 68 => / m l -@= @ = l > ?@ / =@ "; 6= ! 5 ! user?s manual 83 b.1.1 prototyping board features power connection ?a power-supply jack and a 3-pin header are provided for con- nection to the power supply. note that the 3-pin header is symmetrical, with both outer pins connected to ground and the center pin connected to the raw v+ input. the cable of the ac adapter provided with the north american version of the development kit ends in a plug that connects to the power-supply jack (j1). a header plug leading to bare leads is provided for overseas customers to connect their power supply to the 3-pin header (j2)?the center pin of j2 is always connected to the positive terminal, and either edge pin is negative. users providing their own power supply should ensure that it delivers 8?30 v dc at 1 a. regulated power supply ?the raw dc voltage provided at the power in jack is routed to a 5 v switching voltage regulator, then to a separate 3.3 v linear regulator. the regulators provide stable power to the rcm3365/RCM3375 module and the proto- typing board. the voltage regulators will get warm while in use. power led ?the power led lights whenever power is connected to the prototyping board. core led ?the core led lights whenever an rcm3365/RCM3375 module is plugged in correctly on the prototyping board and the rcm3365/RCM3375 module is not being reset. relay led ?the relay led lights whenever the prototyping board relay is energized. reset switch ?a momentary-contact, normally open sw itch is connected directly to the rcm3365/RCM3375?s /reset_in pin. pressing the switch forces a hardware reset of the system. i/o switches and leds ?two momentary-contact, nor mally open switches are con- nected to the pg0 and pg1 pins of the rcm3365/RCM3375 module and may be read as inputs by sample applications. four user leds (ds3?ds6) are connected to alternate i/o bus pins pa0?pa3 pins of the rcm3365/RCM3375 module via u8, and may be driven as output indicators. pe7 and pg5 control the registers in u8 as shown in the sample applications. prototyping area ?a generous prototyping area has been provided for the installation of through-hole components. +3.3 v, +5 v, and ground buses run along one edge of this area. several areas for surface-mount devi ces are also available. each smt pad is connected to a hole designed to accept a 30 awg solid wire. lcd/keypad module ?rabbit?s lcd/keypad module may be plugged in directly to headers lcd1ja, lcd1jb, and lcd1jc. the signals on headers lcd1jb and lcd1jc will be available only if the lc d/keypad module is plugged in to header lcd1ja. appendix c provides complete information for mounting and using the lcd/keypad module. 84 rabbitcore rcm3365/RCM3375 module extension headers ?the complete pin set of the rcm3365/RCM3375 module is duplicated at headers j8 and j9. deve lopers can solder wires directly into the appropriate holes, or, for more flexible development, 2 17 header strips with a 0.1" pitch can be soldered into place. see figure b-4 for the header pinouts. digital i/o ?four digital inputs are available on screw-terminal header j6. see figure b-4 for the header pinouts. rs-232 ?two 3-wire serial ports or one 5-wire rs-232 serial port are available on the prototyping board at screw-terminal header j14. rs-485 ?one rs-485 serial port is available on the prototyping board at screw-termi- nal header j14. quadrature decoder ?four quadrature decoder input s (pf0?pf3) from the rabbit 3000 chip are available on screw-terminal header j5. see figure b-4 for the header pinouts. h-bridge motor driver ?two pairs of h-bridge moto r drivers are supported using screw-terminal headers j3 and j4 on the pr ototyping board for stepper-motor control. see figure b-4 for the header pinouts. rabbitnet port ?one rs-422 rabbitnet port (shared with the serial flash interface) is available to allow rabbitnet peripheral cards to be used with the rcm3365/RCM3375 and the prototyping board. serial flash interface ?one serial flash interface (shared with the rabbitnet port) is available to allow rabbit?s sf1000 series se rial flash to be used on the prototyping board. user?s manual 85 b.2 mechanical dimensions and layout figure b-2 shows the mechanical dimensions and layout for the prototyping board. figure b-2. prototyping board dimensions note: all measurements are in inches followed by millimeters enclosed in parentheses. ! "# "$ "% & ' # $ % ( " )) &* &( )$ )+ $' &, )% -% )* )( !( " . # /# # & /& & # ".! . * #0 #0 1 "! "' "& ") "+ $ # ' & ) + #0 0#+ ' # & $ ) % + ( 0#% ' # & $ ! " . " '2%3$'1 0#( 4#& 4## )& )# &' #, )' $, !" 5 !6 /"/ 0( & ( $ ) % + , * 4+ #' + # # 0& 0# 0) 0+ $ & # '%1 %1 -&-#- # 0% 1/7/# 1/ 1/ 1/7 0$ & 0# $ 0& 1 "! !/' % ( "# ") "+ 5( 5% ( % $ ' 0* $2$1 1/ !/"# ) + "' "$ "% + ) & 5)5+"( /$$'' . !# "!" 0, !& !$ ( $ % $ # ( % $ # 5' 5& ' & ) + ! + & ) & ' + ) & ' 5# 5$ # $ % ( 0 0 !# # & * # ## 0$ #& , #& 0) 0#' # & #) % # #$ 4% #+ #% #( '' '# '& '$ ') '% '+ '( 4 4 ) #$ 4# 4& &,$ 681" &,$ 681" 4* &% &+ &( &* 0#) &) 4#' $* $( $% &+ 0% $+ &$ &# 4, && 0#$ $$ $) #( #* 49% 49# !&': 49& !&': 9& &% 0#& %' -+ ), ) % + ( &, $' $# $& " !& !$ !) !% !+ ;";" ;5;5)*% )*%7 -# -& -$ -) #+ &) &$ && &# "/4 " " 4) $2$1 %1 $2$1 %1 4$ 49) 9# 9#+ 9#( 9#$ 9#) 9#* 9#% 5'< 5'<- 0## ( 4( #* #, &' #) #% 9# 9& %% %+ %( %* +$ +) +% ++ %, +& %# %) ! &$8+ ! &$8+ +( +* +, (' +2(% #(# %2&% #$$ 86 rabbitcore rcm3365/RCM3375 table b-1 lists the electrical, mechanical, and environmental specifications for the proto- typing board. table b-1. prototyping board specifications parameter specification board size 5.25" 6.75" 1.00" (133 mm 171 mm 25 mm) operating temperature ?20c to +70c humidity 5% to 95%, noncondensing input voltage 8 v to 30 v dc maximum current draw (including user-added circuits) 800 ma max. for +3.3 v supply, 1 a total +3.3 v and +5 v combined backup battery cr2032, 3 v lithium coin-type digital inputs 4 inputs pulled up, 36 v dc, switching threshold 0.9?2.3 v typical digital outputs 4 sinking outputs,+30 v dc, 500 ma maximum per channel 8 cmos-level outputs if stepper motor not installed relay spdt relay, 500 ma @ 30 v serial ports two 3-wire rs-232 or one rs-232 with rts/cts one rs-485 other serial interfaces rabbitnet rs-422 port or serial flash interface other interfaces stepper motor control quadrature decoder lcd/keypad module leds seven leds one power on indicator one rcm3365/RCM3375 module indicator four user-configurable leds one relay indicator prototyping area throughhole, 0.1" spacing, additional space for smt components connectors two 2 17, 2 mm pitch sockets for rcm3365/RCM3375 module one 2 5, 2 mm pitch socket for serial flash six screw-terminal headers for serial ports, digital inputs, stepper motor control, quadrature decoder, and relay contacts one rj-45 rabbitnet jack standoffs/spacers 7, accept 4-40 x 1/2 screws user?s manual 87 b.3 power supply the rcm3365/RCM3375 requires a regulated 3.15 v to 3.45 v dc power source to oper- ate. depending on the amount of current requi red by the application, different regulators can be used to supply this voltage. the prototyping board has an onboard +5 v switching power regulator from which a +3.3 v linear regulator draws its supply. thus both +5 v and +3.3 v are available on the prototyping board. the prototyping board itself is protected ag ainst reverse polarity by a diode at d1 as shown in figure b-3. figure b-3. prototyping board power supply ":" "4 :" 0) #'n5 /###( 4) $2$1 $ # & # & $ )''$ # )(n5 $$'n5 %1 # # $$'n6 & # %*#, !: 6 :""4 4# /&%(% #'n5 88 rabbitcore rcm3365/RCM3375 b.4 using the prototyping board the prototyping board is actually both a demonstration board and a prototyping board. as a demonstration board, it can be used with the sample programs to demonstrate the func- tionality of the rcm3365/RCM3375 right out of the box without any modifications. the prototyping board pinouts are shown in figure b-4. figure b-4. prototyping board pinout !( " . " -.' -.( -.* -.. -* -; -. -/ -' -( -& -? -< !# -.1 -./ -.& -.; #! 1/ /) /$ /& /# 1/7 -# -# -& -& %m %1 ' # & $ ;" ;" ;5 ;5 )*% )*%7 4 '' 4 '# 4 '& 4 '$ 4 ') 4 '% 4 '+ 4 '( 1 '< ; &< " )< #<; 5'< <"! $< " < ! +< %< ! < ! ' # & $ ' # & $ ) % + ( !&!$!)!%!+ @ #! " . ! % a $ ;&; $ /?( ' % ) 64 ) 64 $ 64 & 64 # 4 879 1/7 /) /$ /& /# 1/ & /& & # /# # 22 $2$1 1/ !/"# ) + "' "$ "% "( 5+ 5) + ) & "!<4 1 "! !/"' : % ( "# ") "+ 5( 5% ( % $ ' ( $ % $ # ( % $ # 5' 5& ' & ) + ! 4! + & ) & ' + ) & ' 5# 5$ # $ % ( user?s manual 89 the prototyping board comes with the basic components necessary to demonstrate the operation of the rcm3365/RCM3375. four user leds (ds3?ds6) are connected to alternate i/o bus pins pa0?pa3 pins of the rcm3365/RCM3375 module via u8, and may be driven as output indicators when contro lled by pe7 and pg5 as shown in the sample applications. two switches (s2 and s3) are connected to pg0 and pg1 to demonstrate the interface to the rabbit 3000 microprocessor. rese t switch s1 is the hardware reset for the rcm3365/RCM3375. the prototyping board provides the user with rcm3365/RCM3375 connection points brought out conveniently to labeled points at j8 and j9 on the prototyping board. although locations j8 and j9 are unstuffed, 2 17 headers are included in the bag of parts. rs-232 and rs-485 signals are available on screw-terminal header j14, quadrature decoder inputs are available on screw-terminal header j5, and digital inputs are available on screw-terminal header j6. a 1 5 header stri p from the bag of parts may be installed at j12 for four sinking digital outputs. a 1 3 header strip from the bag of parts may be installed at j13 to access selected signals from rcm3000, rcm3100, rcm3200, rcm3300/rcm3310, and rcm3365/RCM3375 rabbitcore modules (j13 cannot be used with the rcm3305/rcm3315). if you don?t plan to use the lcd/keypad module, additional signals may be brought out on 1 5 and 1 8 headers from the bag of parts that you install at j15 and j16. if you don?t plan to use the stepper-motor control option, additi onal cmos outputs are available via a 1 8 header that you install at j10. there is a through-hole prototyping space available on the prototyping board. the holes in the prototyping area are spaced at 0.1" (2.5 mm). +3.3 v, +5 v, and gnd traces run along one edges of the prototyping area . small to medium circuits can be prototyped using point- to-point wiring with 20 to 30 awg wire between the prototyping area, the +3.3 v, +5 v, and gnd traces, and the surrounding area where surface-mount components may be installed. small holes are provided around the surface-m ounted components that may be installed around the prototyping area. b.4.1 adding other components there are two sets of pads for 6-pin, 16-pin, and 28-pin devices that can be used for sur- face-mount prototyping devices. there are also pads that can be used for smt resistors and capacitors in an 0805 smt package. each component has every one of its pin pads connected to a hole in which a 30 awg wire can be soldered (standard wire wrap wire can be soldered in for point-to-point wiring on th e prototyping board). because the traces are very thin, carefully determine which set of hol es is connected to which surface-mount pad. 90 rabbitcore rcm3365/RCM3375 b.4.2 digital i/o b.4.2.1 digital inputs the prototyping board has four digital inputs, in0?in3, each of which is protected over a range of ?36 v to +36 v. the inputs are pulled up to +3.3 v as shown in figure b-5. figure b-5. prototyping board digital inputs the four quadrature decoder inputs on screw-te rminal header j5 may be used as inputs in4?in7. to use the pf0 signal from the ra bbit microprocessor, which goes to qd1b, remember to reconfigure the jumper on header jp3 to jumper pins 1?2. the actual switching threshold is between 0.9 v and 2.3 v. anything below this value is a logic 0, and anything above is a logic 1 . the digital inputs are each fully protected ove r a range of -36 v to +36 v, and can handle short spikes of 40 v. -' && &( $2$1 < user?s manual 91 b.4.3 cmos digital outputs if the stepper-motor option is not used, eight cmos-level digital outputs are available at j10, and can each handle up to 25 ma. b.4.4 sinking digital outputs four sinking digital outputs shared with led s ds3?ds6 are available at j12, and can each handle up to 500 ma. figure b-6 shows a wi ring diagram for a t ypical sinking output. figure b-6. prototyping board sinking digital outputs b.4.5 relay outputs figure b-7 shows the contact connections fo r the relay on the prototyping board. a diode across the coil provides a return path for inductive spikes, and snubbers across the relay contacts protect the relay contacts from inductive spikes. figure b-7. prototyping board relay output contact connections the relay is driven by pin pa4 of the rcm3365/RCM3375 module via u8, and is con- trolled by pe7 and pg5 as shown in the sample applications. 1 $$' # " :6" ! 4 1" ( * , # #' /# # # ) $ & /& & & $2$1 )( #''5 )( #''5 -.* # & $ < )%+ )( #''5 )( #''5 92 rabbitcore rcm3365/RCM3375 b.4.6 serial communication the prototyping board allows you to access up to five of the serial ports from the rcm3365/RCM3375 module. table b-2 summarizes the configuration options. serial port d is configured in software either to allow j7 to be used as a rabbitnet port or to allow j11 to be used as a serial interface for the sf1000 series serial flash. table b-2. prototyping board serial port configurations serial port signal header configured via default use alternate use bj9 ? rcm3365/RCM3375 serial port b signals on pb0, pc4 and pc5 ? cj14 jp5 * * rs-485 termination and bias resist ors are configured via header jp5. rs-485 ? d j7 jp3 rabbitnet (pd2 = 1) rabbit 3000 quadrature decoder j11 sf1000 (pd2 = 0) ej14 ? rs-232 ? fj14 ? rs-232 ? user?s manual 93 b.4.6.1 rs-232 rs-232 serial communication on the prototyping board is supported by an rs-232 trans- ceiver installed at u9. this transceiver pr ovides the voltage output, slew rate, and input voltage immunity required to meet the rs-2 32 serial communication protocol. basically, the chip translates the rabbit 3000?s signals to rs-232 signal levels. note that the polarity is reversed in an rs-232 circuit so that a +5 v output becomes approximately -10 v and 0 v is output as +10 v. the rs-232 transceiver also provides the proper line loading for reliable communication. rs-232 can be used effectively at the rcm3365/RCM3375 module?s maximum baud rate for distances of up to 15 m. rs-232 flow control on an rs-232 port is initiated in software using the serxflowcontrolon function call from rs232.lib , where x is the serial port (e or f). the locations of the flow control lines ar e specified using a set of five macros. serx_rts_port ?data register for the parallel port that the rts line is on (e.g., pgdr). serx_rts_shadow ?shadow register for the rts line's parallel port (e.g., pgdrshadow). serx_rts_bit ?the bit number for the rts line. serx_cts_port ?data register for the parallel port that the cts line is on (e.g., pcdrshadow). serx_cts_bit ?the bit number for the cts line. standard 3-wire rs-232 communication using serial ports e and f is illustrated in the fol- lowing sample code. #define einbufsize 15 // set size of circular buffers in bytes #define eoutbufsize 15 #define finbufsize 15 #define foutbufsize 15 #define mybaud 115200 // set baud rate #endif main(){ sereopen(_mybaud); // open serial ports e and f serfopen(_mybaud); serewrflush(); // flush their input and transmit buffers sererdflush(); serfwrflush(); serfrdflush(); sereclose(_mybaud); // close serial ports c and d serfclose(_mybaud); } 94 rabbitcore rcm3365/RCM3375 b.4.6.2 rs-485 the prototyping board has one rs-485 serial channel, which is connected to the rabbit 3000 serial port c through an rs-485 transcei ver. the half-duplex communication uses an output from pd7 on the rabbit 3000 to control the transmit enable on the communica- tion line. using this scheme a strict master/s lave relationship must exist between devices to insure that no two devices attempt to drive the bus simultaneously. serial port c is configured in software for rs-485 as follows. #define ser485open sercopen #define ser485close sercclose #define ser485wrflush sercwrflush #define ser485rdflush sercrdflush #define ser485putc sercputc #define ser485getc sercgetc #define cinbufsize 15 #define coutbufsize 15 #ifndef _485baud #define _485baud 115200 #endif the configuration shown above is based on circular buffers. rs-485 configuration may also be done using functions from the packet.lib library. the prototyping boards with rcm3365/RCM3375 modules installed can be used in an rs-485 multidrop network spanning up to 1200 m (4000 ft), and there can be as many as 32 attached devices. connect the 485+ to 485+ and 485? to 485? using single twisted-pair wires as shown in figure b-8. note that a common ground is recommended. figure b-8. multidrop network !8)*%7 !)*% !8)*%7 !)*% !8)*%7 !)*% user?s manual 95 the prototyping board comes with a 220 ? termination resistor and two 681 ? bias resis- tors installed and enabled with jumpers across pins 1?2 and 5?6 on header jp5, as shown in figure b-9. figure b-9. rs-485 termination and bias resistors for best performance, the ter mination resistors in a multid rop network should be enabled only on the end nodes of the network, but not on the intervening nodes. jumpers on boards whose termination resistors are not enable d may be stored across pins 1?3 and 4?6 of header jp5. b.4.7 rabbitnet ports the rj-45 jack labeled rabbitnet is a clocked spi rs-422 serial i/o expansion port for use with rabbitnet peripheral boards. the rabbitnet jack does not support ethernet con- nections. header jp3 must have pins 2? 3 jumpered when using the rabbitnet port. the rabbitnet port is enabled in software by setting pd2 = 1. note that the rabbitnet port and the j11 interface cannot be used simultaneously. ! "# "$ "% & ' # $ % ( " )) &* &( )$ )+ $' &, )% -% )* )( !( " . # /# # & /& & # ".! . * #0 #0 1 "! "' "& ") "+ $ # ' & ) + #0 0#+ ' # & $ ) % + ( 0#% ' # & $ ! " . " '2%3$'1 0#( 4#& 4## )& )# &' #, )' $, !" 5 !6 /"/ 0( & ( $ ) % + , * 4+ #' + # # 0& 0# 0) 0+ $ & # '%1 %1 -&-#- # 0% 1/7/# 1/ 1/ 1/7 0$ & 0# $ 0& 1 "! !/' % ( "# ") "+ 5( 5% ( % $ ' 0* $2$1 1/ !/"# ) + "' "$ "% + ) & 5)5+"( /$$'' . !# "!" 0, !& !$ ( $ % $ # ( % $ # 5' 5& ' & ) + ! + & ) & ' + ) & ' 5# 5$ # $ % ( 0 0 !# # & * # ## 0$ #& , #& 0) 0#' # & #) % # #$ 4% #+ #% #( '' '# '& '$ ') '% '+ '( 4 4 ) #$ 4# 4& &,$ 681" &,$ 681" 4* &% &+ &( &* 0#) &) 4#' $* $( $% &+ 0% $+ &$ &# 4, && 0#$ $$ $) #( #* 49% 49# !&': 49& !&': 9& &% 0#& %' -+ ), ) % + ( &, $' $# $& " !& !$ !) !% !+ ;";" ;5;5)*% )*%7 -# -& -$ -) #+ &) &$ && &# "/4 " " 4) $2$1 %1 $2$1 %1 4$ 49) 9# 9#+ 9#( 9#$ 9#) 9#* 9#% 5'< 5'<- 0## ( 4( #* #, &' #) #% 9# 9& %% %+ %( %* +$ +) +% ++ %, +& %# %) ! &$8+ ! &$8+ +( +* +, (' !& $% $+ $( $* )$ !) 4#$ *# (* () # #) #% &+ &( #$ 4& #& ## 0# #' # + * #' ## #% #, &' &) &* $% (( (, (& (' (# *& $# %$ %) )) %* $) &' &# $+ &% &( &# #* #& #$ , 4$ ( & $ + .# , *) ) & % 4# % *' *% (' *+ +) (( %' &, 0, %, #') 4% +( )% #) 4+ 4) #* && 0+ 0( 0* 0) 0% && 0+ ) (, # )& *# *+ (+ 0& $' *& .& -& ,+ +( #'% !$ !# +# &$ 4#+ ) & b $+ +*# $* &&' $( +*# )*% )*%7 + ( 4#' 0% & # + % 0% $ ) % + # & 96 rabbitcore rcm3365/RCM3375 b.4.8 other prototyping board modules an optional lcd/keypad module is availabl e that can be mounted on the prototyping board. the signals on headers lcd1jb and lc d1jc will be available only if the lcd/ keypad module is installed. refer to appe ndix c, ?lcd/keypad module,? for complete information. rabbit?s sf1000 series serial flash may be installed in the socket labeled j11. the j11 interface is enabled in software by setting pd2 = 0. header jp3 must have pins 2?3 jum- pered when using the j11 interface. note that the rabbitnet port and the j11 interface can- not be used simultaneously. b.4.9 quadrature decoder four quadrature decoder inputs are available on screw-terminal header j5. to use the pf0 input from the rabbit microprocessor, which goes to the qd1b input, remember to recon- figure the jumper on header jp3 to jumper pins 1?2. additional information on the use of the quadr ature decoders on parallel port f is pro- vided in the rabbit 3000 microprocessor user?s manual . b.4.10 stepper-motor control the prototyping board can be used to demonstrate the use of the rcm3365/RCM3375 to control a stepper motor. stepper motor control typically directs moves in two orthogonal directions, and so two sets of stepper-motor control circuits are provided for via screw- terminal headers j3 and j4. in order to use the stepper-motor control, install two texas instruments l293dn chips at locations u2 and u3 (shown in figure b-10). these chips are readily available from your favorite electronics parts source, and may be purchased through our web store as part number 660-0205. figure b-10. install four-channel push-pull driver chips ! " # " $ " % & ' # $ % ( " )) &* &( )$ )+ $' &, )% -% )* )( !( " . # / # # & / & & # ".! . * #0 #0 1 " ! " ' " & " ) " + $ # ' & ) + #0 0#+ ' # & $ ) % + ( 0#% ' # & $ ! " . " '2%3$'1 0#( 4#& 4## )& )# &' #, )' $, ! " 5 ! 6 / " / 0( & ( $ ) % + , * 4+ #' + # # 0& 0# 0) 0+ $ & # '%1 %1 -&-#- # 0% 1/7/# 1/ 1/ 1/7 0$ & 0# $ 0& 1 "! !/' % ( "# ") "+ 5( 5% ( % $ ' 0* $2$1 1/ !/"# ) + "' "$ "% + ) & 5 ) 5 + " ( /$$'' . !# "!" 0, !& !$ ( $ % $ # ( % $ # 5' 5& ' & ) + ! + & ) & ' + ) & ' 5# 5$ # $ % ( 0 0 ! # # & * # ## 0 $ #& , #& 0) 0#' # & #) % # #$ 4% #+ #% #( '' '# '& '$ ') '% '+ '( 4 4 ) #$ 4# 4& &,$ 681" &,$ 681" 4* &% &+ &( &* 0#) &) 4#' $* $( $% &+ 0% $+ &$ &# 4, && 0#$ $$ $) #( #* 49% 49# !&': 49& !&': 9& &% 0#& %' -+ ), ) % + ( &, $' $# $& " !& !$ !) !% !+ ;";" ;5;5)*% )*%7 -# -& -$ -) #+ &) &$ && &# "/4 " " 4) $2$1 %1 $2$1 %1 4$ 49) 9# 9#+ 9#( 9#$ 9#) 9#* 9#% 5'< 5'<- 0## ( 4( #* #, &' #) #% 9# 9& % % % + % ( % * + $ + ) + % + + %, +& %# %) ! &$8+ ! &$8+ +( +* +, (' !& $% $+ $( $* )$ !) 4#$ *# (* () # #) #% &+ &( #$ 4& #& ## 0# #' # + * #' ## #% #, &' &) &* $% (( (, (& (' (# *& $# %$ %) )) %* $) &' &# $+ &% &( &# #* #& #$ , 4$ ( & $ + .# , *) ) & % 4# % *' *% (' *+ +) (( %' &, 0, %, #') 4% +( )% #) 4+ 4) #* && 0+ 0( 0* 0) 0% && 0+ ) (, # )& *# *+ (+ 0& $' *& .& -& ,+ +( #'% ! $ ! # +# &$ 4#+ ) & user?s manual 97 figure b-11 shows the stepper-motor driver circuit. figure b-11. stepper-motor driver circuit the stepper motor(s) can be powered either from the onboard power supply or from an external power based on the jumper settings on headers jp1 and jp2. table b-3. stepper motor power-supply options header pins connected factory default jp1 1?2 9?10 onboard power supply to u2 3?4 7?8 external power supply to u2 jp2 1?2 9?10 onboard power supply to u3 3?4 7?8 external power supply to u3 0$ & $ ) 4& % # + $ + ## #) & # ( #' , #% " "# " "& / l / 7 l &( &( &,$ 1/ /# /& /$ /) 1/8 4 # 4 & 4 $ 4 ) # & $ ) &( &( 0) & $ ) 4$ % # + $ + ## #) & # ( #' , #% " "# " "& / l / 7 l &( &( &,$ 1/8 /# /& /$ /) 1/ < 4 # 4 & 4 $ 4 ) # & $ ) &( &( < 5) 5% 5+ 5( 98 rabbitcore rcm3365/RCM3375 b.5 prototyping board jumper configurations figure b-12 shows the header locations used to configure the various prototyping board options via jumpers. figure b-12. location of prototyping board configurable positions 0$ 0) 0% 0# 0& user?s manual 99 table b-4 lists the configuration options using jumpers. table b-4. prototyping board jumper configurations header description pins connected factory default jp1 stepper motor power-supply options (u2) 1?2 9?10 onboard power supply 3?4 7?8 external power supply jp2 stepper motor power-supply options (u3) 1?2 9?10 onboard power supply 3?4 7?8 external power supply jp3 pf0 option 1?2 quadrature decoder inputs enabled 2?3 rabbitnet/serial flash interface enabled jp4 rcm3365/RCM3375 power supply 2?3 rcm3365/RCM3375 powered via prototyping board jp5 rs-485 bias and termination resistors 1?2 5?6 bias and termination resistors connected 1?3 4?6 bias and termination resistors not connected (parking position for jumpers) 100 rabbitcore rcm3365/RCM3375 b.6 use of rabbit 3000 parallel ports table b-5 lists the rabbit 3000 parallel ports and their use for the prototyping board. table b-5. prototyping board use of rabbit 3000 parallel ports port i/o use initial state pa0?pa3 data bus lcd/keypad module, motor driver, leds active high pa4 data bus lcd/keypad module, motor driver, relay and relay led active high pa5?pa7 data bus lcd/keypad module, motor control active high pb0 input clkb, xd-picture card detect high pb1 input clka programming port high (when not driven by clka) pb2?pb5 address bus lcd/keypad module high pb6?pb7 address bus ? high pc0 output txd spi, serial flash serial port d high (spi disabled) pc1 input rxd spi, serial flash high (spi disabled) pc2 output txc rs-485 serial port c high (rs-485 disabled) pc3 input rxc rs-485 high (rs-485 disabled) pc4 * output txb serial port b high (disabled) pc5 * input rxb high (disabled) pc6 output txa programming port serial port a high pc7 input rxa programming port high pd0 output rcm3365/RCM3375 usr led off (shared with nand flash busy) high pd1 output soldered-in nand flash chip enable high (disabled) pd2 output spi, serial flash low (spi disabled) pd3 output spi, serial flash high (spi cs disabled) pd4?pd6 input serial flash high (disabled) pd7 output rs-485 tx enable low (rs-485 tx disabled) pe0?pe1 input in0?in1 high pe2 output ethernet aen, nand flash function enable high (disabled) pe3 output motor driver a clock pulse low (disabled) pe4?pe5 input in2?in3, j8 high pe6 output lcd/keypad module high (disabled) user?s manual 101 pe7 output motor driver b clock pulse high (disabled) pf0 input spi, serial flash, quadrature decoder high pf1?pf3 input quadrature decoder high pf4?pf7 output motor 1?4 control low (disabled) pg0 input switch s1 high pg1 input switch s2 high pg2 input txf rs-232 serial port f high (rs-232 disabled) pg3 input rxf rs-232 high (rs-232 disabled) pg4 output motor driver a enable high (disabled) pg5 output motor driver b enable high (disabled) pg6 input txe rs-232 serial port e high (rs-232 disabled) pg7 input rxe rs-232 high (rs-232 disabled) * not used with rcm3365/RCM3375. table b-5. prototyping board use of rabbit 3000 parallel ports (continued) port i/o use initial state 102 rabbitcore rcm3365/RCM3375 user?s manual 103 a ppendix c. lcd/k eypad m odule an optional lcd/keypad is availa ble for the prototyping board. appendix c describes the lcd/keypad and provides the soft- ware function calls to make full use of the lcd/keypad. c.1 specifications two optional lcd/keypad modules?with or without a panel-mounted nema 4 water- resistant bezel?are available for use with the prototyping board. they are shown in figure c-1. figure c-1. lcd/keypad modules versions only the version without the bezel can mount directly on the prototyping board; if you have the version with a bezel, you will have to remove the bezel to be able to mount the lcd/keypad module on the prototyping board. ei ther version of the lcd/keypad module can be installed at a remote location up to 60 cm (24") away. contact your rabbit sales representative or your authorized distributor for further assistance in purchasing an lcd/ keypad module. # )c % 104 rabbitcore rcm3365/RCM3375 mounting hardware and a 60 cm (24") extens ion cable are also available for the lcd/ keypad module through your sales represen tative or authorized distributor. table c-1 lists the electrical, mechanical, and environmental specifications for the lcd/ keypad module. table c-1. lcd/keypad specifications parameter specification board size 2.60" x 3.00" x 0.75" (66 mm x 76 mm x 19 mm) bezel size 4.50" 3.60" 0.30" (114 mm 91 mm 7.6 mm) temperature operating range: 0c to +50c storage range: ?40c to +85c humidity 5% to 95%, noncondensing power consumption 1.5 w maximum * * the backlight adds approximately 650 mw to the power consumption. connections connects to high-rise header sockets on the prototyping board lcd panel size 122 32 graphic display keypad 7-key keypad leds seven user-programmable leds the lcd/keypad module has 0.1" idc headers at j1, j2, and j3 for physical connection to other boards or ribbon cables. figure c-2 shows the lcd/keypad module footprint. these values are relative to one of the mounting holes. note: all measurements are in inches followed by millimeters enclosed in parentheses. all dimen- sions have a manufacturing toler- ance of 0.01" (0.25 mm). figure c-2. user board footprint for lcd/keypad module -; -. '2&'' %2# '2#'' &2% '2%'' #&2( #2)%' $+2* -& &2&'' %%2, #2+'' )'2+ '2(+* #,2% '2+'( #%2) user?s manual 105 c.2 contrast adjustments for all boards starting in 2005, lcd/keypad modules were factory-configured to optimize their contrast based on the voltage of the system they woul d be used in. be sure to select a kdu3v lcd/keypad module for use with the prototyping board for the rcm3365/RCM3375 ? these modules operate at 3.3 v. you may adjust the contrast using the potentiometer at r2 as shown in figure c-3. lcd/keypad modules co nfigured for 5 v may be used with the 3.3 v prototyping board, but the backlight will be dim. figure c-3. lcd/keypad module contrast adjustments you can set the contrast on the lcd displa y of pre-2005 lcd/keypad modules by adjust- ing the potentiometer at r2 or by setting the voltage for 3.3 v by connecting the jumper across pins 3?4 on header j5 as shown in fi gure c-3. only one of these two options is available on these lcd/keypad modules. note: older lcd/keypad modules that do not have a header at j5 or a contrast adjust- ment potentiometer at r2 are limited to operate only at 5 v, and will not work with the prototyping board for the rcm3365/RCM3375. the older lcd/keypad modules are no longer being sold. & & # $ & # # % 4& 0# $ 4# ) #' # + #$ #& ( * &% &+ ## #$ #) #' , #& #% #* -* #+ -% &# -& 4% 0& ! . 0) # #( -) && -+ &$ -( &' -$ #, 4( #) &) #% #+ 4+ 4) ( , 4$ # ## ) % + 0# -# 0% #( # 0% $%'' &2*1 6" $2$1 # & $ ) 22c%1 # )c % - $ (# " " ""#$ / # * ) ! # 0% # & $ ) 2#'#8'%)# / 106 rabbitcore rcm3365/RCM3375 c.3 keypad labeling the keypad may be labeled according to your ne eds. a template is provided in figure c-4 to allow you to design your own keypad label insert. figure c-4. keypad template to replace the keypad legend, remove the old legend and insert your new legend prepared according to the template in figure c-4. th e keypad legend is located under the blue key- pad matte, and is accessible from the left only as shown in figure c-5. figure c-5. removing and inserting keypad label the sample program keybasic.c in the 122x32_1x7 folder in samples\lcd_keypad shows how to reconfigure the keypad for different applications. #2#' &* &2$% +' ?=k = k@?= 2 user?s manual 107 c.4 header pinouts figure c-6 shows the pinouts for the lcd/keypad module. figure c-6. lcd/keypad module pinouts c.4.1 i/o address assignments the lcd and keypad on the lcd/keypad modul e are addressed by the /cs strobe as explained in table c-2. table c-2. lcd/keypad module address assignment address function 0xe000 device select base address (/cs) 0xexx0?0xexx7 lcd control 0xexx8 led enable 0xexx9 not used 0xexxa 7-key keypad 0xexxb (bits 0?6) 7-led driver 0xexxb (bit 7) lcd backlight on/off 0xexxc?exxf not used + ) & ' # $ "( "% "$ "# "! 1 ( % $ # ' & "+ ") "& ! % 4 "+ ") "& "( % "( "% "$ "# "! 1 ( % $ # ' & + ) & ' # $ 108 rabbitcore rcm3365/RCM3375 c.5 mounting lcd/keypad module on the prototyping board install the lcd/keypad module on header sock ets lcd1ja, lcd1jb, and lcd1jc of the prototyping board as shown in figure c-7. be careful to align the pins over the headers, and do not bend them as you press down to mate the lcd/keypad module with the proto- typing board. figure c-7. install lcd/keypad module on prototyping board ! "# "$ "% & ' # $ % ( 9#' 9## 9#& " )) &* &( )$ )+ $' &, )% -% )* )( !( " . # /# # & /& & # ".! . * #0 #0 1 "! "' "& ") "+ $ # ' & ) + #0 0#+ ' # & $ ) % + ( 0#% ' # & $ ! " . " '2%3$'1 0#( 4#& 4## )& )# &' #, )' $, #* #, &' !" 5 !6 /"/ #) #% 0## 0( & ( $ ) % + , * 4+ #' + 4( ( $ ) # # 0& 0# 0) 0+ $ & # '%1 %1 -&-#-# 0% 1/7/# 1/ 1/ 1/7 0$ & 0# $ 0& 1 "! !/' % ( "# ") "+ 5( 5% ( % $ ' 0* $2$1 1/ !/"# ) + "' "$ "% + ) & 5)5+"( /$$'' . !# "!" 0, !& !$ ( $ % $ # ( % $ # 5' 5& ' & ) + ! + & ) & ' + ) & ' 5# 5$ # $ % ( 0 0 !# # & * # ## 9( 9* 9, 9) 9% 9+ # & 0$ 9# 9& 9$ % #& , #& 0) 0#' + ( #) % # #$ 4% #+ #% $ #( '#&$)%+( 4 4 ) #$ 4# 4& &,$ 681" &,$ 681" 4* &% &+ &( &* 0#) &) 4#' $* $( $% &+ 0% $+ &$ &# 4, && 0#$ $$ $) #( #* 49% 49) 49$ 49# 49& 9& 9#+ 9#( 9#* 9#$ 9#) 9#% 9# &% 0#& %' -+ ), ) % + ( &, $' $# $& " !& !$ !) !% !+ ;";" ;5;5)*% )*%7 -# -& -$ -) #+ &) &$ && &# "/4 " " 4) $2$1 %1 $2$1 %1 4$ +4 !& $% $+ $( $* )$ !) 4#$ *# (* () # #) #% &+ &( #$ 4& #& ## 0# #' # + * #' ## #% #, &' &) &* $% (( (, (& (' (# *& $# %$ %) )) %* $) &' &# $+ &% &( &# #* #& #$ , 4$ ( & $ + .# , *) ) & % 4# % *' *% (' *+ +) (( %' &, 0, %, #') 4% +( )% #) 4+ 4) #* && 0+ 0( 0* 0) 0% && 0+ ) (, # )& *# *+ (+ 0& $' *& .& -& ,+ +( #'% !$ !# +# &$ 4#+ ) & +4 +4 user?s manual 109 c.6 bezel-mount installation this section describes a nd illustrates how to bezel-mount the lcd/keypad module designed for remote insta llation. follow these steps for bezel-mount installation. 1. cut mounting holes in the mounting panel in accordance with the recommended dimen- sions in figure c-8, then use the bezel f aceplate to mount the lcd/keypad module onto the panel. figure c-8. recommended cutout dimensions 2. carefully ?drop in? the lcd/keypad module with the bezel and gasket attached. $2)'' *+2) $2#'' (*2* &2*(' (&2, '2&$' %2* '2#&%d); $ @,4@, '2#$' $2$ 110 rabbitcore rcm3365/RCM3375 3. fasten the unit with the four 4-40 screws and washers included with the lcd/keypad module. if your panel is thick, use a 4-40 sc rew that is approximately 3/16" (5 mm) longer than the thickness of the panel. figure c-9. lcd/keypad module mounted in panel (rear view) carefully tighten the screws until the gasket is compressed and the plastic bezel face- plate is touching the panel. do not tighten each screw fully before moving on to the next screw. apply only one or two turns to each screw in sequence until all are tightened manually as far as they can be so that the gasket is compressed and the plastic bezel faceplate is touching the panel. d ) 7 ! . 4# 4& # & $ ) 4$ #( 0# -# # # & $ ) , #' ## -& -$ -) #& % + -% -+ #$ ( #) * #% #* -( -* % #+ + 0$ 4) # 0& * ( # user?s manual 111 c.6.1 connect the lcd/keypad module to your prototyping board the lcd/keypad module can be located as far as 2 ft. (60 cm) away from the prototyping board, and is connected via a ribbon cable as shown in figure c-10. figure c-10. connecting lcd/keypad module to prototyping board note the locations and connections relative to pin 1 on both the prototyping board and the lcd/keypad module. rabbit offers 2 ft. (60 cm) extension cables. contact your authorized distributor or a rab- bit sales representative for more information. ! "# "$ "% & ' # $ % ( 9#' 9## 9#& " )) &* &( )$ )+ $' &, )% -% )* )( !( " . # /# # & /& & # ".! . * #0 #0 1 "! "' "& ") "+ $ # ' & ) + #0 0#+ ' # & $ ) % + ( 0#% ' # & $ ! " . " '2%3$'1 0#( 4#& 4## )& )# &' #, )' $, #* #, &' !" 5 !6 /"/ #) #% 0## 0( & ( $ ) % + , * 4+ #' + 4( ( $ ) # # 0& 0# 0) 0+ $ & # '%1 %1 -& -#-# 0% 1/7 /# 1/ 1/ 1/7 0$ & 0# $ 0& 1 "! !/' % ( "# ") "+ 5( 5% ( % $ ' 0* $2$1 1/ !/"# ) + "' "$ "% + ) & 5)5+"( /$$'' . !# "!" 0, !& !$ ( $ % $ # ( % $ # 5' 5& ' & ) + ! + & ) & ' + ) & ' 5# 5$ # $ % ( 0 0 !# # & * # ## 9( 9* 9, 9) 9% 9+ # & 0$ 9# 9& 9$ % #& , #& 0) 0#' + ( #) % # #$ 4% #+ #% $ #( '#&$)%+( 4 4 ) #$ 4# 4& &,$ 681" &,$ 681" 4* &% &+ &( &* 0#) &) 4#' $* $( $% &+ 0% $+ &$ &# 4, && 0#$ $$ $) #( #* 49% 49) 49$ 49# 49& 9& 9#+ 9#( 9#* 9#$ 9#) 9#% 9# &% 0#& %' -+ ), ) % + ( &, $' $# $& " !& !$ !) !% !+ ;";" ;5;5)*% )*%7 -# -& -$ -) #+ &) &$ && &# "/4 " " 4) $2$1 %1 $2$1 %1 4$ & & # $ & # # % 4& 0# $ 4# ) #' # + #$ #& ( * &% &+ ## #$ #) #' , #& #% #* -* #+ -% &# -& 4% 0& ! . 0) # #( -) && -+ &$ -( &' -$ #, 4( #) &) #% #+ 4+ 4) ( , 4$ # ## ) % + 0# -# 0% #( # 0% $%'' &2*1 6" $2$1 # & $ ) 22c%1 +4 !& $% $+ $( $* )$ !) 4#$ *# (* () # #) #% &+ &( #$ 4& #& ## 0# #' # + * #' ## #% #, &' &) &* $% (( (, (& (' (# *& $# %$ %) )) %* $) &' &# $+ &% &( &# #* #& #$ , 4$ ( & $ + .# , *) ) & % 4# % *' *% (' *+ +) (( %' &, 0, %, #') 4% +( )% #) 4+ 4) #* && 0+ 0( 0* 0) 0% && 0+ ) (, # )& *# *+ (+ 0& $' *& .& -& ,+ +( #'% !$ !# +# &$ 4#+ ) & # # 112 rabbitcore rcm3365/RCM3375 c.7 sample programs sample programs illustrating the use of the lcd/keypad module with the prototyping board are provided in the samples\rcm3360\lcd_keypad folder. these sample programs use the external i/o bus on the rabbit 3000 chip, and so the #define porta_aux_io line is already included in the sample programs. each sample program has comments that de scribe the purpose and function of the pro- gram. follow the instructions at the beginni ng of the sample program. to run a sample program, open it with the file menu (if it is not still open), then compile and run it by pressing f9 . the rcm3365/RCM3375 must be connected to a pc using the serial programming cable (you also have the option to use an ethernet cable if the rcm3365 is rabbitsys-enabled) as described in chapter 2, ?getting started.? complete information on dynamic c is provided in the dynamic c user?s manual . keypadtoled.c ?this program demonstrates the us e of the external i/o bus. the program will light up an led on the lcd/keypad module and will display a message on the lcd when a key press is detect ed. the ds3, ds4, ds5, and ds6 leds on the prototyping board will also light up. the red led (ds3) on the rcm3365 module will also light up. lcdkeyfun.c ?this program demonstrates how to draw primitive features from the graphic library (lines, circles, polygons), and also demonstrates the keypad with the key release option. switchtolcd.c ?this program demonstrates the us e of the external i/o bus. the program will light up an led on the lcd/keypad module and will display a message on the lcd when a switch press is detected. the ds1 and ds2 leds on the prototyp- ing board will also light up. additional sample programs are available in the samples\lcd_keypad\122x32_1x7 folder. user?s manual 113 c.8 lcd/keypad module function calls when mounted on the prototyping board, the lcd/keypad module uses the external i/o bus on the rabbit 3000 chip. remember to add the line #define porta_aux_io to the beginning of any programs using the external i/o bus. c.8.1 lcd/keypad module initialization the function used to initialize the lcd/keypad module can be found in the dynamic c lib\displays\lcd122key7.lib library. initializes the lcd/keypad module. the keypad is set up using keypaddef() or keyconfig() after this function call. return value none. c.8.2 leds when power is applied to the lcd/keypad m odule for the first time, the red led (ds1) will come on, indicating that power is bei ng applied to the lcd/keypad module. the red led is turned off when the brdinit function executes. one function is available to control the leds, and can be found in the dynamic c lib\ displays\lcd122key7.lib library. led on/off control. this function will only work when the lcd/keypad module is installed on the prototyping board. parameters led is the led to control. 0 = led ds1 1 = led ds2 2 = led ds3 3 = led ds4 4 = led ds5 5 = led ds6 6 = led ds7 value is the value used to control whether the led is on or off (0 or 1). 0 = off 1 = on return value none. void dispinit(); void displedout(int led, int value); 114 rabbitcore rcm3365/RCM3375 c.8.3 lcd display the functions used to control the lcd display are contained in the graphic.lib library located in the dynamic c lib\displays\graphic library folder. when x and y coordi- nates on the display screen are specified, x can range from 0 to 121, and y can range from 0 to 31. these numbers represent pixels from the top left corner of the display. initializes the display devices, clears the screen. return value none. see also gldisponoff, glbacklight, glsetcontrast, glplotdot, glblock, glplotdot, glplotpolygon, glplotcircle, glhscroll, glvscroll, glxfontinit, glprintf, glputchar, glsetbrushtype, glbufflock, glbuffunlock, glplotline turns the display backlight on or off. parameter onoff turns the backlight on or off 1?turn the backlight on 0?turn the backlight off return value none. see also glinit, gldisponoff, glsetcontrast sets the lcd screen on or off. data will not be cleared from the screen. parameter onoff turns the lcd screen on or off 1?turn the lcd screen on 0?turn the lcd screen off return value none. see also glinit, glsetcontrast, glbacklight void glinit(void); void glbacklight(int onoff); void gldisponoff(int onoff); user?s manual 115 sets display contrast. note: this function is not used with the lcd/keypad module since the support circuits are not available on the lcd/keypad module. fills the lcd display screen with a pattern. parameter the screen will be set to all black if pattern is 0xff, all white if pattern is 0x00, and vertical stripes for any other pattern. return value none. see also glblock, glblankscreen, glplotpolygon, glplotcircle blanks the lcd display screen (sets lcd display screen to white). return value none. see also glfillscreen, glblock, glplotpolygon, glplotcircle draws a rectangular block in the page buffer and on the lcd if the buffer is unlocked. any portion of the block that is outside the lcd display area will be clipped. parameters x is the x coordinate of the top left corner of the block. y is the y coordinate of the top left corner of the block. bmwidth is the width of the block. bmwidth is the height of the block. return value none. see also glfillscreen, glblankscreen, glplotpolygon, glplotcircle void glsetcontrast(unsigned level); void glfillscreen(char pattern); void glblankscreen(void); void glblock(int x, int y, int bmwidth, int bmheight); 116 rabbitcore rcm3365/RCM3375 plots the outline of a polygon in the lcd page buffer, and on the lcd if the buffer is unlocked. any portion of the polygon that is outside the lcd display area will be clipped. if fewer than 3 vertices are specified, the function will return without doing anything. parameters n is the number of vertices. *pfirstcoord is a pointer to array of vertex coordinates: x1,y1, x2,y2, x3,y3,... return value none. see also glplotpolygon, glfillpolygon, glfillvpolygon plots the outline of a polygon in the lcd page buffer and on the lcd if the buffer is unlocked. any portion of the polygon that is outside the lcd display area will be clipped. if fewer than 3 vertices are specified, the function will return without doing anything. parameters n is the number of vertices. y1 is the y coordinate of the first vertex. x1 is the x coordinate of the first vertex. y2 is the y coordinate of the second vertex. x2 is the x coordinate of the second vertex. ... are the coordinates of additional vertices. return value none. see also glplotvpolygon, glfillpolygon, glfillvpolygon void glplotvpolygon(int n, int *pfirstcoord); void glplotpolygon(int n, int y1, int x2, int y2, ...); user?s manual 117 fills a polygon in the lcd page buffer and on the lcd screen if the buffer is unlocked. any portion of the polygon that is outside the lcd display area will be clipped. if fewer than 3 vertices are specified, the function will return without doing anything. parameters n is the number of vertices. *pfirstcoord is a pointer to array of vertex coordinates: x1,y1, x2,y2, x3,y3,... return value none. see also glfillpolygon, glplotpolygon, glplotvpolygon fills a polygon in the lcd page buffer and on the lcd if the buffer is unlocked. any portion of the polygon that is outside the lcd display area will be clipped. if fewer than 3 vertices are specified, the function will return without doing anything. parameters n is the number of vertices. x1 is the x coordinate of the first vertex. y1 is the y coordinate of the first vertex. x2 is the x coordinate of the second vertex. y2 is the y coordinate of the second vertex. ... are the coordinates of additional vertices. return value none. see also glfillvpolygon, glplotpolygon, glplotvpolygon draws the outline of a circle in the lcd page buffer and on the lcd if the buffer is unlocked. any por- tion of the circle that is outside the lcd display area will be clipped. parameters xc is the x coordinate of the center of the circle. yc is the y coordinate of the center of the circle. rad is the radius of the center of the circle (in pixels). return value none. see also glfillcircle, glplotpolygon, glfillpolygon void glfillvpolygon(int n, int *pfirstcoord); void glfillpolygon(int n, int x1, int y1, int x2, int y2, ...); void glplotcircle(int xc, int yc, int rad); 118 rabbitcore rcm3365/RCM3375 draws a filled circle in the lcd page buffer and on the lcd if the buffer is unlocked. any portion of the circle that is outside the lcd display area will be clipped. parameters xc is the x coordinate of the center of the circle. yc is the y coordinate of the center of the circle. rad is the radius of the center of the circle (in pixels). return value none. see also glplotcircle, glplotpolygon, glfillpolygon initializes the font descriptor structure, where the font is stored in xmem . parameters *pinfo is a pointer to the font descriptor to be initialized. pixwidth is the width (in pixels) of each font item. pixheight is the height (in pixels) of each font item. startchar is the value of the first printable character in the font character set. endchar is the value of the last printable character in the font character set. xmembuffer is the xmem pointer to a linear array of font bitmaps. return value none. see also glprinf void glfillcircle(int xc, int yc, int rad); void glxfontinit(fontinfo *pinfo, char pixwidth, char pixheight, unsigned startchar, unsigned endchar, unsigned long xmembuffer); user?s manual 119 returns the xmem address of the character from the specified font set. parameters *pinfo is the xmem address of the bitmap font set. letter is an ascii character. return value xmem address of bitmap character font , column major, and byte-aligned. see also glputfont, glprintf puts an entry from the font table to the page buffer and on the lcd if the buffer is unlocked. each font character's bitmap is column major and byte-aligned. any portion of the bitmap character that is outside the lcd display area will be clipped. parameters x is the x coordinate (column) of the top left corner of the text. y is the y coordinate (row) of the top left corner of the text. *pinfo is a pointer to the font descriptor. code is the ascii character to display. return value none. see also glfontcharaddr, glprintf sets the glprintf() printing step direction. the x and y step directions are independent signed values. the actual step increments depend on the height and width of the font being displayed, which are multi- plied by the step values. parameters stepx is the glprintf x step value stepy is the glprintf y step value return value none. see also use glgetpfstep() to examine the current x and y printing step direction. unsigned long glfontcharaddr(fontinfo *pinfo, char letter); void glputfont(int x, int y, fontinfo *pinfo, char code); void glsetpfstep(int stepx, int stepy); 120 rabbitcore rcm3365/RCM3375 gets the current glprintf() printing step direction. each step di rection is independent of the other, and is treated as an 8-bit signed value. the actual step increments depends on the height and width of the font being displayed, which are multiplied by the step values. return value the x step is returned in the msb, and the y step is returned in the lsb of the integer result. see also use glgetpfstep() to control the x and y printing step direction. provides an interface between the stdio string-handling functions an d the graphic library. the stdio string-formatting function will call this function, one character at a time, until the entire format- ted string has been parsed. any portion of the bitmap character that is outside the lcd display area will be clipped. parameters ch is the character to be displayed on the lcd. *ptr is not used, but is a place holder for stdio string functions. *cnt is not used, is a place holder for stdio string functions. *pinst is a font descriptor pointer. return value none. see also glprintf, glputfont, doprnt int glgetpfstep(void); void glputchar(char ch, char *ptr, int *cnt, glputcharinst *pinst) user?s manual 121 prints a formatted string (much like printf ) on the lcd screen. only the character codes that exist in the font set are printed, all others are skipped. for ex ample, '\b', '\t', '\n' and '\r' (ascii backspace, tab, new line, and carriage return, respectively) will be printed if they exist in the font set, but will not have any effect as control characters. any portion of the bitmap character that is outside the lcd display area will be clipped. parameters x is the x coordinate (column) of the top left corner of the text. y is the y coordinate (row) of the top left corner of the text. *pinfo is a font descriptor pointer. *fmt is a formatted string. ... are formatted string conversion parameter(s). example glprintf(0,0, &fi12x16, "test %d\n", count); return value none. see also glxfontinit increments lcd screen locking counter. graphic calls are recorded in the lcd memory buffer and are not transferred to the lcd if the counter is non-zero. note: glbufflock() and glbuffunlock() can be nested up to a level of 255, but be sure to balance the calls. it is not a requirement to use these procedures, but a set of glbufflock() and glbuffunlock() bracketing a set of related graphic calls speeds up the rendering significantly. return value none. see also glbuffunlock, glswap decrements the lcd screen locking counter. the cont ents of the lcd buffer are transferred to the lcd if the counter goes to zero. return value none. see also glbufflock, glswap void glprintf(int x, int y, fontinfo *pinfo, char *fmt, ...); void glbufflock(void); void glbuffunlock(void); 122 rabbitcore rcm3365/RCM3375 checks the lcd screen locking counter . the contents of the lcd buffer are transferred to the lcd if the counter is zero. return value none. see also glbuffunlock, glbufflock, _glswapdata (located in the library specifically for the lcd that you are using) sets the drawing method (or color) of pixels drawn by subsequent graphic calls. parameter type value can be one of the following macros. pixblack draws black pixels (turns pixel on). pixwhite draws white pixels (turns pixel off). pixxor draws old pixel xor'ed with the new pixel. return value none. see also glgetbrushtype gets the current method (or color) of pixels drawn by subsequent graphic calls. return value the current brush type. see also glsetbrushtype draws a single pixel in the lcd buffer, and on the lc d if the buffer is unlocked. if the coordinates are outside the lcd display area, the dot will not be plotted. parameters x is the x coordinate of the dot. y is the y coordinate of the dot. return value none. see also glplotline, glplotpolygon, glplotcircle void glswap(void); void glsetbrushtype(int type); int glgetbrushtype(void); void glplotdot(int x, int y); user?s manual 123 draws a line in the lcd buffer, and on the lcd if the buffer is unlocked. any portion of the line that is beyond the lcd display area will be clipped. parameters x0 is the x coordinate of one endpoint of the line. y0 is the y coordinate of one endpoint of the line. x1 is the x coordinate of the other endpoint of the line. y1 is the y coordinate of the other endpoint of the line. return value none. see also glplotdot, glplotpolygon, glplotcircle scrolls byte-aligned window left one pixel, right column is filled by current pixel type (color). parameters left is the top left corner of bitmap, must be evenly divisible by 8, otherwise truncates. top is the top left corner of the bitmap. cols is the number of columns in the window, must be evenly divisible by 8, otherwise truncates. rows is the number of rows in the window. return value none. see also glhscroll, glright1 scrolls byte-aligned window right one pixel, left column is filled by current pixel type (color). parameters left is the top left corner of bitmap, must be evenly divisible by 8, otherwise truncates. top is the top left corner of the bitmap. cols is the number of columns in the window, must be evenly divisible by 8, otherwise truncates. rows is the number of rows in the window. return value none. see also glhscroll, glleft1 void glplotline(int x0, int y0, int x1, int y1); void glleft1(int left, int top, int cols, int rows); void glright1(int left, int top, int cols, int rows); 124 rabbitcore rcm3365/RCM3375 scrolls byte-aligned window up one pixel, bottom co lumn is filled by current pixel type (color). parameters left is the top left corner of bitmap, must be evenly divisible by 8, otherwise truncates. top is the top left corner of the bitmap. cols is the number of columns in the window, must be evenly divisible by 8, otherwise truncates. rows is the number of rows in the window. return value none. see also glvscroll, gldown1 scrolls byte-aligned window down one pixel, top column is filled by current pixel type (color). parameters left is the top left corner of bitmap, must be evenly divisible by 8, otherwise truncates. top is the top left corner of the bitmap. cols is the number of columns in the window, must be evenly divisible by 8, otherwise truncates. rows is the number of rows in the window. return value none. see also glvscroll, glup1 void glup1(int left, int top, int cols, int rows); void gldown1(int left, int top, int cols, int rows); user?s manual 125 scrolls right or left, within the defined window by x number of pixels. the opposite edge of the scrolled window will be filled in with white pixels. the window must be byte-aligned. parameters will be verified for the following: 1. the left and cols parameters will be verified that they are evenly divisible by 8. if not, they will be truncated to a value that is a multiple of 8. 2. parameters will be checked to verify that the scrolling area is valid. the minimum scrolling area is a width of 8 pixels and a height of one row. parameters left is the top left corner of bitmap, must be evenly divisible by 8. top is the top left corner of the bitmap. cols is the number of columns in the window, must be evenly divisible by 8. rows is the number of rows in the window. npix is the number of pixels to scroll within the defined window (a negative value will produce a scroll to the left). return value none. see also glvscroll void glhscroll(int left, int top, int cols, int rows, int npix); 126 rabbitcore rcm3365/RCM3375 scrolls up or down, within the defined window by x number of pixels. the opposite edge of the scrolled window will be filled in with white pixels. the window must be byte-aligned. parameters will be verified for the following: 1. the left and cols parameters will be verified that they are evenly divisible by 8. if not, they will be truncated to a value that is a multiple of 8. 2. parameters will be checked to verify that th e scrolling area is valid. the minimum scrolling area is a width of 8 pixels and a height of one row. parameters left is the top left corner of bitmap, must be evenly divisible by 8. top is the top left corner of the bitmap. cols is the number of columns in the window, must be evenly divisible by 8. rows is the number of rows in the window. npix is the number of pixels to scroll within the defined window (a negative value will produce a scroll up). return value none. see also glhscroll draws bitmap in the specified space. th e data for the bitmap are stored in xmem . this function calls glxputfastmap automatically if th e bitmap is byte-aligned (the le ft edge and the width are each evenly divisible by 8). any portion of a bitmap image or character that is outside the lcd display area will be clipped. parameters left is the top left corner of the bitmap. top is the top left corner of the bitmap. width is the width of the bitmap. height is the height of the bitmap. bitmap is the address of the bitmap in xmem . return value none. see also glxputfastmap, glprintf void glvscroll(int left, int top, int cols, int rows, int npix); void glxputbitmap(int left, int top, int width, int height, unsigned long bitmap); user?s manual 127 draws bitmap in the specified space. th e data for the bitmap are stored in xmem . this function is like glxputbitmap , except that it is faster. the restriction is that the bitmap must be byte-aligned. any portion of a bitmap image or character that is outside the lcd display area will be clipped. parameters left is the top left corner of the bitmap, must be evenly divisible by 8, otherwise truncates. top is the top left corner of the bitmap. width is the width of the bitmap, must be evenly divisible by 8, otherwise truncates. height is the height of the bitmap. bitmap is the address of the bitmap in xmem . return value none. see also glxputbitmap, glprintf defines a text-only display window. this function provides a way to display characters within the text window using only character row and column coordina tes. the text window feature provides end-of-line wrapping and clipping after the character in the last column and row is displayed. note: execute the textwindowframe function before other text... functions. parameters *window is a window frame descriptor pointer. *pfont is a font descriptor pointer. x is the x coordinate of the top left corner of the text window frame. y is the y coordinate of the top left corner of the text window frame. winwidth is the width of the text window frame. winheight is the height of the text window frame. return value 0?window frame was successfully created. -1? x coordinate + width has exceeded the display boundary. -2? y coordinate + height has exceeded the display boundary. void glxputfastmap(int left, int top, int width, int height, unsigned long bitmap); int textwindowframe(windowframe *window, fontinfo *pfont, int x, int y, int winwidth, int winheight) 128 rabbitcore rcm3365/RCM3375 sets the cursor location to displa y the next character. the display location is based on the height and width of the character to be displayed. note: execute the textwindowframe function before using this function. parameters *window is a pointer to a font descriptor. col is a character column location. row is a character row location. return value none. see also textputchar, textprintf, textwindowframe gets the current cursor locatio n that was set by a graphic text... function. note: execute the textwindowframe function before using this function. parameters *window is a pointer to a font descriptor. *col is a pointer to cursor column variable. *row is a pointer to cursor row variable. return value lower word = cursor row location upper word = cursor column location see also textgotoxy, textprintf, textwindowframe, textcursorlocation void textgotoxy(windowframe *window, int col, int row); void textcursorlocation(windowframe *window, int *col, int *row); user?s manual 129 displays a character on the display where the cursor is currently pointing. if any portion of a bitmap character is outside the lcd display area, the character will not be displayed. the cursor increments its position as needed. note: execute the textwindowframe function before using this function. parameters *window is a pointer to a font descriptor. ch is a character to be displayed on the lcd. return value none. see also textgotoxy, textprintf, textwindowframe, textcursorlocation prints a formatted string (much like printf ) on the lcd screen. only prin table characters in the font set are printed, also escape sequences, '\r' and '\n' are recognized. all other escape sequences will be skipped over; for example, '\b' and 't' will print if they exist in the font set, but will not have any effect as control characters. the text window feature provides end-of-line wrapping and clipping after the character in the last col- umn and row is displayed. the cursor then remains at the end of the string. note: execute the textwindowframe function before using this function. parameters *window is a pointer to a font descriptor. *fmt is a formatted string. ... are formatted string conversion parameter(s). example textprintf(&textwindow, "test %d\n", count); return value none. see also textgotoxy, textputchar, textwindowframe, textcursorlocation void textputchar(struct windowframe *window, char ch); void textprintf(struct windowframe *window, char *fmt, ...); 130 rabbitcore rcm3365/RCM3375 c.8.4 keypad the functions used to control the keypad are contained in the keypad7.lib library located in the dynamic c keypads library folder. initializes keypad process return value none. see also brdinit assigns each key with key press and release codes, and hold and repeat ticks for auto repeat and debouncing. parameters craw is a raw key code index. 1x7 keypad matrix with raw key code index assignments (in brackets): user keypad interface cpress is a key press code an 8-bit value is returned when a key is pressed. 0 = unused. see keypaddef() for default press codes. crelease is a key release code. an 8-bit value is returned when a key is pressed. 0 = unused. ccnthold is a hold tick, which is approximately one debounce period or 5 s. how long to hold before repeating. 0 = no repeat. cspdlo is a low-speed repeat tick, which is approximately one debounce period or 5 s. how many times to repeat. 0 = none. ccntlo is a low-speed hold tick, which is approximately one debounce period or 5 s. how long to hold before going to high-speed repeat. 0 = slow only. void keyinit(void); void keyconfig(char craw, char cpress, char crelease, char ccnthold, char cspdlo, char ccntlo, char cspdhi); [0] [1] [2] [3] [4] [5] [6] user?s manual 131 cspdhi is a high-speed repeat tick, which is approximately one debounce period or 5 s. how many times to repeat after low speed repeat. 0 = none. return value none. see also keyprocess, keyget, keypaddef scans and processes keypad data for key assignment, debouncing, press and release, and repeat. note: this function is also able to process an 8 x 8 matrix keypad. return value none see also keyconfig, keyget, keypaddef get next keypress. return value the next keypress, or 0 if none see also keyconfig, keyprocess, keypaddef pushes the value of ckey to the top of the input queue, which is 16 bytes deep. parameter ckey return value none. see also keyget void keyprocess(void); char keyget(void); int keyunget(char ckey); 132 rabbitcore rcm3365/RCM3375 configures the physical layout of the keypad with the default ascii return key codes. keypad physical mapping 1 x 7 where 'd' represents down scroll 'u' represents up scroll 'r' represents right scroll 'l' represents left scroll '?' represents page down '+' represents page up 'e' represents the enter key example: do the followingfor the above physical vs. ascii return key codes. keyconfig ( 3,'r',0, 0, 0, 0, 0 ); keyconfig ( 6,'e',0, 0, 0, 0, 0 ); keyconfig ( 2,'d',0, 0, 0, 0, 0 ); keyconfig ( 4,'-',0, 0, 0, 0, 0 ); keyconfig ( 1,'u',0, 0, 0, 0, 0 ); keyconfig ( 5,'+',0, 0, 0, 0, 0 ); keyconfig ( 0,'l',0, 0, 0, 0, 0 ); characters are returned upon keypress with no repeat. return value none. see also keyconfig, keyget, keyprocess writes "1" to each row and reads the va lue. the position of a keypress is indicated by a zero value in a bit position. parameter *pckeys is a pointer to the ad dress of the value read. return value none. see also keyconfig, keyget, keypaddef, keyprocess void keypaddef(); 0415263 ['l'] ['u'] ['d'] ['r'] ['?'] ['+'] ['e'] void keyscan(char *pckeys); user?s manual 133 a ppendix d. p ower s upply appendix d provides information on the current requirements of the rcm3365/RCM3375 modules, and includes some background on the reset generator. d.1 power supplies power is supplied from the motherboard to which the rcm3365/RCM3375 is connected via header j4. the rcm3365/RCM3375 require a regulated 3.15 v to 3.45 v dc power source. an rcm3365/RCM3375 with no loading at the outputs operating at 44.2 mhz typically draws 250 ma. d.1.1 battery backup the rcm3365/RCM3375 does not have a battery, but there is provision for a customer- supplied battery to back up the data sram and keep the internal rabbit 3000 real-time clock running. note: a backup battery is highly recommended to back up the data sram when using an rcm3365 with dynamic c rabbitsys to keep rabbitsys from reverting to its default settings in case of a power failure. header j4, shown in figure d-1, allows access to the external battery. this header makes it possible to connect an external 3 v power supply. this allows the sram and the inter- nal rabbit 3000 real-time clock to retain data with the rcm3365/RCM3375 powered down. figure d-1. external battery connections at header j4 1/ $2$1 $' $# &, $& 1 <"9 "; 134 rabbitcore rcm3365/RCM3375 a lithium battery with a nominal voltage of 3 v and a minimum capacity of 165 mah is recommended. a lithium battery is strongly re commended because of its nearly constant nominal voltage over most of its life. the drain on the battery by the rcm3365/RCM3375 is typically 6 a when no other power is supplied. if a 165 mah battery is used, the battery can last about 3 years: the rcm3365/RCM3375 module does not drain the battery while it is powered up normally. cycle the main power off/on on the rcm3365/RCM3375 after you install a backup battery for the first time, and whenever you replace the battery. this step will minimize the current drawn by the real-time clock oscillator circuit from the backup battery should the rcm3365/RCM3375 experience a loss of main power. note: remember to cycle the main power off/on any time the rcm3365/RCM3375 is removed from the prototyping board or motherboard since that is where the backup battery would be located. rabbit?s technical note tn235, external 32.768 khz oscillator circuits , provides addi- tional information about the current draw by the real-time clock oscillator circuit. d.1.2 battery-backup circuit figure d-2 shows the battery-backup circuit. figure d-2. rcm33365/RCM3375 backup battery circuit the battery-backup circuit serves three purposes: it reduces the battery voltage to the sram and to the real-time clock, thereby limiting the current consumed by the real-time clock and lengthening the battery life. it ensures that current can flow only out of the battery to prevent charging the battery. a voltage, vosc, is supplied to u1, which keeps the 32.768 khz oscillator working when the voltage begins to drop. 165 mah 6 a ----------------------- - 3.1 years. = 1/ #%' )+ 1 8"9 0 - ( )( 1! # $ #'' & #''5 % #'5 user?s manual 135 d.1.3 reset generator the rcm3365/RCM3375 uses a reset generator to reset the rabbit 3000 microprocessor when the voltage drops below the voltage necessary for relia ble operation. the reset occurs between 2.85 v and 3.00 v, typically 2.93 v. the rcm3365/RCM3375 has a reset pin, pin 28 on header j4. this pin provides access to the reset input of the reset generator, whos e output drives the reset input of the rabbit 3000 and peripheral circuits. the /reset output from the reset generator is available on pin 1 of header j4 on the rcm3365/RCM3375, and can be used to reset user-defined cir- cuits on the motherboard on which the rcm3365/RCM3375 module is mounted. 136 rabbitcore rcm3365/RCM3375 user?s manual 137 a ppendix e. p rogramming via e thernet c rossover c able a rabbitsys-enabled rcm3365 module can also be pro- grammed with a cat5/6 ethernet crossover cable connecting the rcm3365 module directly to a pc or notebook. this appen- dix describes the connection and how to set up the tcp/ip parameters. section 2, ?getting started,? describes how to connect a pc, notebook, or workstation to an rcm3365 module via a serial programming ca ble or via a cat 5/6 ethernet cable. a cat 5/6 crossover ethernet cable can be used to connect an rcm3365 module directly to a pc, notebook, or workstation, but the tcp/ip parameters have to be entered into the rcm3365 module and on to the pc, notebook, or workstation if the pc, notebook, or workstation does not have a dhcp server. this appendix explains how to load the tcp/ip parameters when the pc, notebook, or workst ation if the pc, notebook, or workstation does not have a dhcp server. 138 rabbitcore rcm3365/RCM3375 e.1 load tcp/ip parameters to the rcm3365 module 1. connect the 10-pin prog connector of the serial programming cable to header j1 on the rcm3365 module as described in section 2.2.2. (do not use the diag connector.) 2. use the file menu to open the sample program setupforcrossover.c , which is in the dynamic c samples\rabbitsys folder. press function key f9 to compile and run the program. this sample program brings down the ethernet interface, turns off dhcp, sets the rcm3365's ip address to 10.10.6.100, sets th e netmask to 255.255.255.0, and sets the default gateway to 10.10.6.1. the rcm3365 module is now set up. the ip and gateway addresses ca n be changed in the two macros in the two macros at the beginning of the sample program: #define _ipaddr"10.10.6.100" #define _gateway"10.10.6.1" to restore the rcm3365 to its defa ult dhcp behavior, uncomment the enable_dhcp macro: //#define enable_dhcp user?s manual 139 e.2 load tcp/ip parameters to the pc, notebook, or workstation if the pc, notebook, or workstation is connected to a network, disconnect it from the network. check with your administrator if you are unable to change the settings as described here since you may need administrator privileges. the screen shots shown here are from windows 2000, and the interface is similar for other versions of windows. 1. go to the control panel ( start > settings > control panel ) and start network connections . 2. select the network interface card used for the ethernet interface you intend to use (e.g., tcp/ip xircom credit card net- work adapter ) and click on the ?proper- ties? button. depending on which version of windows your pc is running, you may have to select the ?local area connec- tion? first, and then click on the ?proper- ties? button to bring up the ethernet interface dialog. then ?configure? your interface card for a ?10base-t half- duplex? or an ?auto-negotiation? con- nection on the ?advanced? tab. note: your network interface card will likely have a different name. 140 rabbitcore rcm3365/RCM3375 4. click user?s manual 141 e.3 run a program you are now ready to run a sample program or develop a new application. review these steps to check your dynamic c rabbits ys setup before you run a program. 1. set the compiler to run the application in the fast program execution sram by select- ing code and bios in flash, run in ram from the dynamic c options > project options > compiler menu. 2. enable separate instruction and data spaces and select ?compile program in rabbitsys user mode? from the dynamic c options > project options > compiler menu. 3. enter the rcm3365 module?s ip address you used in appendix e.1 by accessing the dynamic c options > project options > communications menu to select ?use tcp/ ip connection.? you must also enter ?32023? for the control port and the default login values of ?admin? and ?password.? e.3.1 troubleshooting if you compiled and ran a sample program with the rabbitsys project option disabled, you may have overwritten the rabbitsys bina ry file. use the serial programming cable to connect programming header j1 on th e rcm3365 to your pc com port to reload the rabbitsys binary file via the dynamic c compile > reload rabbitsys binary menu. if you were unable to reload the rabbitsys binary file, your rcm3365 does not have the firmware to support dynamic c rabbitsys and cannot be used with dynamic c rabbitsys. if dynamic c returns an error message, check that the rcm3365 is powered correctly ? the red core led on the prototyping board should be lit when the rcm3365 is mounted on the prototyping board and the ac adapter is plugged in. ensure that the rcm3365 module is firmly and correctly inst alled in its connectors on the prototyping board. note: the rdiscover utility will not work when the rcm3365 is connected directly to a pc, notebook, or workstation via an ethernet crossover cable unless the pc, notebook, or workstation is running a dhcp server. 142 rabbitcore rcm3365/RCM3375 user?s manual 143 a ppendix f. r abbit n et f.1 general rabbitnet description rabbitnet is a high-speed synchronous protoc ol developed by rabb it to connect periph- eral cards to a master and to allow them to communicate with each other. f.1.1 rabbitnet connections all rabbitnet connections are made point to point. a rabbitnet master port can only be connected directly to a peripheral card, and the number of peripheral cards is limited by the number of available rabbitnet ports on the master. figure f-1. connecting peripheral cards to a master %,!$ #3! #3! %,!$ #3! '' # === < - ( " "" !" !" " "" !" 144 rabbitcore rcm3365/RCM3375 use a straight-through ethernet cable to connect the master to slave peripheral cards, unless you are using a device such as the op7200 that could be used either as a master or a slave. in this case you would use a crossover cable to connect an op7200 that is being used as a slave. distances between a master unit and peri pheral cards can be up to 10 m or 33 ft. f.1.2 rabbitnet peripheral cards digital i/o 24 inputs, 16 push/pull outputs, 4 channels of 10-bit a/d conversion with ranges of 0 to 10 v, 0 to 1 v, and -0.25 to +0.25 v. the following connectors are used: signal = 0.1" friction-lock connectors power = 0.156" friction-lock connectors rabbitnet = rj-45 connector a/d converter 8 channels of programmable-ga in 12-bit a/d conversion, configurable as current mea- surement and differential-input pairs. 2.5 v reference voltage is available on the con- nector. the following connectors are used: signal = 0.1" friction-lock connectors power = 0.156" friction-lock connectors rabbitnet = rj-45 connector d/a converter 8 channels of 0?10 v 12-bit d/a convers ion. the following connectors are used: signal = 0.1" friction-lock connectors power = 0.156" friction-lock connectors rabbitnet = rj-45 connector display/keypad interface allows you to connect your own keypad with up to 64 keys and one character liquid crystal display from 1 8 to 4 40 character s with or without backlight using standard 1 16 or 2 8 connectors . the following connectors are used: signal = 0.1" headers or sockets power = 0.156" friction-lock connectors rabbitnet = rj-45 connector relay card 6 relays rated at 250 v ac, 1200 va or 100 v dc up to 240 w. the following connectors are used : relay contacts = screw-terminal connectors power = 0.156" friction-lock connectors rabbitnet = rj-45 connector visit our web site for up-to-date information about additional cards and features as they become available. the web site also has the latest revision of this user?s manual. user?s manual 145 f.2 physical implementation there are four signaling functi ons associated with a rabbitnet connection. from the mas- ter?s point of view, the transmit function carries information and commands to the periph- eral card. the receive function is used to read back information sent to the master by the peripheral card. a clock is used to synchroni ze data going between the two devices at high speed. the master is the source of this clock. a slave select (ss) function originates at the master, and when detected by a peripheral car d causes it to become selected and respond to commands received from the master. the signals themselves are differential rs-422, which are series-terminated at the source. with this type of termination, the maximu m frequency is limited by the round-trip delay time of the cable. although a peripheral card could theoretically be up to 45 m (150 ft) from the master for a data rate of 1 mhz, rabbit recommends a practical limit of 10 m (33 ft). connections between peripheral cards and ma sters are done using standard 8-conductor ethernet cables. masters and peripheral card s are equipped with rj-45 8-pin female con- nectors. the cables may be swapped end for end without affecting functionality. f.2.1 control and routing control starts at the master when the master asserts the slave select signal (ss). then it simultaneously sends a serial command and cloc k. the first byte of a command contains the address of the peripheral card if more than one peripheral card is connected. a peripheral card assumes it is selected as soon as it receives the select signal. for direct master-to-peripheral-card connections, this is as soon as the master asserts the select sig- nal. the connection is established once the se lect signal reaches the addressed slave. at this point communication between the master and the selected peripheral card is estab- lished, and data can flow in both directions simultaneously. the connection is maintained so long as the master asserts the select signal. 146 rabbitcore rcm3365/RCM3375 f.3 function calls the function calls described in this section are used with all rabbitnet peripheral cards, and are available in the rnet.lib library in the dynamic c rabbitnet folder. resets, initializes, or disables a specified rabbitnet port on the master single-board computer. during initialization, the network is enumerated and relevant tables are filled in. if the port is already initialized, calling this function forces a re-enumeration of all devices on that port. call this function first before using other rabbitnet functions. parameters portflag is a bit that represents a rabbitnet port on the master single-board computer (from 0 to the maximum number of ports). a set bit requires a service. if portflag = 0x03, both rabbitnet ports 0 and 1 will need to be serviced. servicetype enables or disables each rabbitnet port as set by the port flags. 0 = disable port 1 = enable port return value 0 returns an address index to device information from a given physical node address. this function will check device information to dete rmine that the peripheral card is connected to a master. parameter pna is the physical node address, indicated as a byte. 7,6?2-bit binary representation of the port number on the master 5,4,3?level 1 router downstream port 2,1,0?level 2 router downstream port return value pointer to device information. -1 indicates that the pe ripheral card either cannot be identified or is not connected to the master. see also rn_find int rn_init(char portflag, char servicetype); int rn_device(char pna); user?s manual 147 locates the first active device that matches the search criteria. parameter srch is the search criteria structure rn_search: unsigned int flags; // status flags see match macros below unsigned int ports; // port bitmask char productid; // product id char productrev; // product rev char coderev; // code rev long serialnum; // serial number use a maximum of 3 macros for the search criteria: rn_match_port // match port bitmask rn_match_pna // match physical node address rn_match_handle // match instance (reg 3) rn_match_prdid // match id/version (reg 1) rn_match_prdrev // match product revision rn_match_coderev // match code revision rn_match_sn // match serial number for example: rn_search newdev; newdev.flags = rn_match_port|rn_match_sn; newdev.ports = 0x03; //search ports 0 and 1 newdev.serialnum = e3446c01l; handle = rn_find(&newdev); return value returns the handle of the first device matching the criteria. 0 indicates no such devices were found. see also rn_device the peripheral card sends back the character the master sent. this function will check device information to determine that the peripheral card is connected to a master. parameters handle is an address index to device information. use rn_device() or rn_find() to establish the handle. sendecho is the character to echo back. recdata is a pointer to the return address of the character from the device. return value the status byte from the previous command. -1 m eans that device information indicates the peripheral card is not connected to the master. int rn_find(rn_search *srch); int rn_echo(int handle, char sendecho, char *recdata); 148 rabbitcore rcm3365/RCM3375 writes a string to the specified device and register. waits for results. this function will check device infor- mation to determine that the periphe ral card is connected to a master. parameters handle is an address index to device information. use rn_device() or rn_find() to establish the handle. regno is the command register number as designated by each device. data is a pointer to the address of the string to write to the device. datalen is the number of bytes to write (0?15). note: a data length of 0 will transmit the one-byte command register number. return value the status byte from the previous command. -1 m eans that device information indicates the peripheral card is not connected to the master, and -2 means that the data length was greater than 15. see also rn_read reads a string from the specified device and register. waits for results. this function will check device information to determine that the peri pheral card is connected to a master. parameters handle is an address index to device information. use rn_device() or rn_find() to establish the handle. regno is the command register number as designated by each device. recdata is a pointer to the address of the string to read from the device. datalen is the number of bytes to read (0?15). note: a data length of 0 will transmit the one-byte command register number. return value the status byte from the previous command. -1 m eans that device information indicates the peripheral card is not connected to the master, and -2 means that the data length was greater than 15. see also rn_write int rn_write(int handle, int regno, char *data, int datalen); int rn_read(int handle, int regno, char *recdata, int datalen); user?s manual 149 sends a reset sequence to the specified peripheral car d. the reset takes approximately 25 ms before the peripheral card will once again execute the application. allow 1.5 seconds after the reset has completed before accessing the peripheral card. this function will check peripheral card information to determine that the peripheral card is connected to a master. parameters handle is an address index to device information. use rn_device() or rn_find() to establish the handle. resettype describes the type of reset. 0 = hard reset?equivalent to power-up. all logic is reset. 1 = soft reset?only the microprocessor logic is reset. return value the status byte from the previous command. -1 m eans that device information indicates the peripheral card is not connected to the master. sets software watchdog timeout period. call this function prior to enabling the software watchdog timer. this function will check device information to dete rmine that the peripheral car d is connected to a master. parameters handle is an address index to device information. use rn_device() or rn_find() to establish the handle. timeout is a timeout period from 0.025 to 6.375 seconds in increments of 0.025 seconds. entering a zero value will disable the software watchdog timer. return value the status byte from the previous command. -1 m eans that device information indicates the peripheral card is not connected to the master. int rn_reset(int handle, int resettype); int rn_sw_wdt(int handle, float timeout); 150 rabbitcore rcm3365/RCM3375 enables the hardware and/or software watchdog timers on a peripheral card. the software on the periph- eral card will keep the hardware watchdog timer updated, but will hard reset if the time expires. the hardware watchdog cannot be disabled except by a ha rd reset on the peripheral card. the software watch- dog timer must be updated by software on the master. the peripheral card will soft reset if the timeout set by rn_sw_wdt() expires. this function will check device information to determine that the peripheral card is connected to a master. parameters handle is an address index to device information. use rn_device() or rn_find() to establish the handle. wdttype 0 enables both hardware and software watchdog timers 1 enables hardware watchdog timer 2 enables software watchdog timer return value the status byte from the previous command. -1 m eans that device information indicates the peripheral card is not connected to the master. see also rn_hitwd, rn_sw_wdt hits software watchdog. set the timeout period and enable the software watchdog prior to using this function. this function will check device information to determine that the peripheral card is connected to a master. parameters handle is an address index to device information. use rn_device() or rn_find() to establish the handle. count is a pointer to return the present count of the software watchdog timer. the equivalent time left in seconds can be determined from count 0.025 seconds. return value the status byte from the previous command. -1 m eans that device information indicates the peripheral card is not connected to the master. see also rn_enable_wdt, rn_sw_wdt int rn_enable_wdt(int handle, int wdttype); int rn_hitwd(int handle, char *count); user?s manual 151 reads the status of which reset occurred and whether any watchdogs are enabled. parameters handle is an address index to device information. use rn_device() or rn_find() to establish the handle. retdata is a pointer to the return address of the communication byte. a set bit indicates which error occurred. this register is cleared when read. 7?hw reset has occurred 6?sw reset has occurred 5?hw watchdog enabled 4?sw watchdog enabled 3,2,1,0?reserved return value the status byte from the previous command. parameters handle is an address index to device information. use rn_device() or rn_find() to establish the handle. retdata is a pointer to the return address of the communication byte. a set bit indicates which error occurred. this register is cleared when read. 7?data available and waiting to be processed mosi (master out, slave in) 6?write collision miso (master in, slave out) 5?overrun mosi (master out, slave in) 4?mode fault, device detected hardware fault 3?data compare error detected by device 2,1,0?reserved return value the status byte from the previous command. int rn_rst_status(int handle, char *retdata); int rn_comm_status(int handle, char *retdata); 152 rabbitcore rcm3365/RCM3375 f.3.1 status byte unless otherwise specified, functions returning a status byte will have the following format for each designated bit. 7 6 5 4 3 2 1 0 00 = reserved 01 = ready 10 = busy 11 = device not connected 0 = device 1 = router 0 = no error 1 = communication error * * use the function rn_comm_status() to determine which error occurred. reserved for individual peripheral cards reserved for individual peripheral cards 0 = last command accepted 1 = last command unexecuted 0 = not expired 1 = hw or sw watchdog timer expired ? ? use the function rn_rst_status() to determine which timer expired. user?s manual 153 i ndex symbols /iowr loading .............................. 32 a accessories connector adapter board ... 7 usb removable memory card reader .................... 7 additional information online documentation .......... 7 b battery backup circuit .............................. 134 external battery connec- tions ............................ 133 reset generator ................. 135 use of battery-backed sram ....................................... 44 board initialization function calls ..................... 46 brdinit ............................ 46 bus loading ............................ 73 c clock doubler ........................ 40 conformal coating ........... 79, 80 connector adapter board ....... 7 d development kit rabbitsys development kit 7 rcm3365/RCM3375 .......... 6 32 mb nand flash ........ 6 ac adapter ...................... 6 dc power supply ............ 6 getting started instruc- tions .............................. 6 programming cable ......... 6 digital i/o .............................. 28 function calls digin .............................. 47 digout ........................... 47 i/o buffer sourcing and sink- ing limits ....................... 77 memory interface .............. 33 smode0 .......................... 35 smode1 .......................... 35 digital inputs switching threshold ........... 90 dimensions lcd/keypad module ....... 103 lcd/keypad template ..... 106 prototyping board ............. 85 rcm3365/RCM3375 ........ 68 dynamic c .............. 7, 9, 14, 41 add-on modules ............. 9, 52 installation ....................... 9 battery-backed sram ...... 44 fat file system ................ 45 libraries rcm33xx.lib .............. 46 rn_cfg_rcm33.lib . 46 protected variables ............ 44 rabbit embedded security pack ...................... 7, 9, 52 sample programs ............... 20 standard features debugging ...................... 42 telephone-based technical support ...................... 7, 52 upgrades and patches ........ 52 usb/serial port converter . 15 e ethernet cables ...................... 53 how to tell them apart ....... 53 ethernet connections ....... 53, 55 10/100base-t .................... 55 10base-t ethernet card .... 53 additional resources .......... 65 direct connection ............... 55 ethernet cables .................. 55 ethernet hub ...................... 53 ip addresses ................ 55, 57 mac addresses ................. 58 steps .................................. 54 ethernet port ......................... 34 pinout ................................ 34 exclusion zone ...................... 69 external i/o bus .................... 33 software ............... 33, 44, 113 f features .................................... 2 comparison with rcm3305/ rcm3315 ....................... 4 prototyping board ....... 82, 83 flash memory addresses user blocks ........................ 38 h hardware connections install rcm3365/RCM3375 on prototyping board ... 10 power supply ..................... 13 programming cable ........... 11 hardware reset ....................... 13 headers prototyping board jp3 ................................. 92 jp5 ................................. 95 i i/o address assignments lcd/keypad module ....... 107 i/o buffer sourcing and sinking limits ............................. 77 ip addresses .......................... 57 how to set in sample programs ....................................... 62 how to set pc ip address .. 63 154 rabbitcore rcm3365/RCM3375 j jumper configurations prototyping board jp1 (stepper motor power supply) ........................99 jp2 (stepper motor power supply) ........................99 jp3 (quadrature decoder/ serial flash) .................99 jp4 (rcm3365/RCM3375 power supply) .............99 jp5 (rs-485 bias and termi- nation resistors) ....95, 99 stepper motor power supply .....................................97 rcm3365/RCM3375 ..78, 79 jp2 (flash memory bank select) ..........................79 jp3 (data sram size) ...79 jp4 (ethernet or i/o output on header j3) ...............79 jp5 (ethernet or i/o output on header j3) ...............79 jp6 (ethernet or i/o output on header j3) ...............79 jp7 (ethernet or i/o output on header j3) ...............79 jp8 (ethernet or i/o output on header j3) ...............79 jp9 (chip select signals for nand flash and xd- picture card) ...............79 jumper locations ............78 r96 (xd-picture card detect) .........................79 k keypad template ..................106 removing and inserting label ......................................106 l lcd/keypad module bezel-mount installation ..109 dimensions .......................103 function calls dispinit .........................113 header pinout ...................107 i/o address assignments ..107 keypad function calls keyconfig ................130 keyget ......................131 keyinit ......................130 keypaddef ................132 keyprocess ...............131 keyscan ....................132 keyunget ..................131 keypad template ..............106 lcd display function calls glbacklight .............114 glblankscreen ..........115 glblock ....................115 glbufflock ..............121 glbuffunlock ...........121 gldisponoff ............114 gldown1 ..................124 glfillcircle ...............118 glfillpolygon ...........117 glfillscreen ..............115 glfillvpolygon ........117 glfontcharaddr .......119 glgetbrushtype ......122 glgetpfstep ..............120 glhscroll ..................125 glinit ........................114 glleft1 .....................123 glplotcircle ..............117 glplotdot ..................122 glplotline ................123 glplotpolygon ..........116 glplotvpolygon .......116 glprintf .....................121 glputchar .................120 glputfont .................119 glright1 ...................123 glsetbrushtype .......122 glsetcontrast ...........115 glsetpfstep ..............119 glswap .....................122 glup1 .......................124 glvscroll ..................126 glxfontinit ..............118 glxputbitmap ..........126 glxputfastmap ........127 textcursorlocation .128 textgotoxy ............128 textprintf .................129 textputchar .............129 textwindowframe ..127 leds function calls ...............113 displedout ................113 mounting instructions ......108 reconfigure keypad ..........106 remote cable connection ..111 removing and inserting keypad label .............................106 sample programs .............112 specifications ...................104 versions ...........................103 voltage settings ................105 led (prototyping board) function calls ledout ............................48 leds (rcm3365/RCM3375) 33 act ...................................33 fm .....................................33 link .................................33 speed ...............................33 usr ...................................33 m mac addresses .....................58 mounting instructions lcd/keypad module .......108 p peripheral cards connection to master 143, 144 pinout ethernet port ......................34 lcd/keypad module .......107 rcm3365/RCM3375 alternate configurations .30 rcm3365/RCM3375 headers .......................................28 power supplies +3.3 v ..............................133 battery backup .................133 program mode .......................36 switching modes ................36 programming cable prog connector ...............36 rcm3365/RCM3375 connec- tions ...............................11 programming option ethernet crossover cable .137 troubleshooting ............141 programming port .................35 user?s manual 155 prototyping board ................. 82 adding components ........... 89 dimensions ........................ 85 expansion area ................... 83 features ........................ 82, 83 jumper configurations ....... 99 jumper locations ................ 98 mounting rcm3365/ RCM3375 ..................... 10 power supply ..................... 87 prototyping area ................ 89 specifications .................... 86 use of parallel ports ......... 100 r rabbit 3000 data and clock delays ........ 75 spectrum spreader time delays ....................................... 75 rabbit subsystems ................ 29 rabbitnet ethernet cables to connect peripheral cards .. 143, 144 function calls rn_comm_status .......... 151 rn_device ..................... 146 rn_echo ........................ 147 rn_enable_wdt ............. 150 rn_find ......................... 147 rn_hitwd ...................... 150 rn_init .......................... 146 rn_read ........................ 148 rn_reset ........................ 149 rn_rst_status ................ 151 rn_sw_wdt ................... 149 rn_write ....................... 148 general description .......... 143 peripheral cards ............... 144 a/d converter .............. 144 d/a converter .............. 144 digital i/o .................... 144 display/keypad interface ................................... 144 relay card ..................... 144 physical implementation . 145 rabbitnet port ................... 95 rabbitnet port function calls ..................... 50 macros ........................... 50 rn_sp_close .................... 51 rn_sp_disable ................ 51 rn_sp_enable ................. 51 rn_sp_info ..................... 50 rabbitsys .............................. 43 check whether rcm3365 has rabbitsys firmware 17, 141 dynamic c setup ....... 16, 141 troubleshooting ................. 17 rcm3309/rcm3319 comparison with rcm3305/ rcm3315 ....................... 4 rcm3365/RCM3375 mounting on prototyping board ............................ 10 relay function calls relayout ......................... 49 remote programming ............ 43 download manager ............ 43 rabbitlink ........................ 43 rabbitsys .......................... 43 reset ....................................... 13 use of reset pin ................ 135 rs-485 network termination and bias resistors ....................................... 95 run mode ............................. 36 switching modes ............... 36 s sample programs ................... 20 download manager dlm_tcp.c ................. 43 dlp_tcp.c .................. 43 getting to know the rcm3365/RCM3375 controlled.c ........ 20 flashled1.c ............ 20 swrelay.c ................ 20 toggleswitch.c .... 20 hot-swapping xd-picture card fat_hot_swap.c ..... 23 fat_hot_swap_3365_ 75.c ............................. 23 fat_hot_swap_ 336x0.c ....................... 39 how to run tcp/ip sample programs ................. 61, 62 how to set ip address ........ 62 how to use non-rcm3365/ RCM3375 rabbitnet sample programs ........... 26 lcd/keypad module . 26, 112 keybasic.c ............. 106 keypadtoled.c .... 112 lcdkeyfun.c ......... 112 reconfigure keypad ...... 106 switchtolcd.c .... 112 nand flash nflash_dump.c ....... 21 nflash_erase.c ...... 22 nflash_inspect.c .. 21 nflash_log.c ......... 21 pong.c ...................... 15, 16 rabbitnet .......................... 26 real-time clock rtc_test.c ................ 25 setrtckb.c .............. 25 serial communication flowcontrol.c ..... 24 parity.c .................... 24 simple3wire.c ........ 24 simple485master.c 25 simple485slave.c .. 25 simple5wire.c ........ 24 switchchar.c ........ 25 setupforcrossover.c ..................................... 138 tcp/ip browseled.c .......... 64 display_mac.c ....... 58 mboxdemo.c ........... 64 pingled.c .................. 65 pingme.c .................... 64 rabbitweb blinkleds.c ......... 65 doormonitor.c . 65 sprinkler.c ......... 65 smtp.c ........................ 65 user-programmable led flashled.c .............. 33 serial communication ............ 34 function calls ser485rx ....................... 49 ser485tx ....................... 49 prototyping board rs-232 .......................... 93 rs-485 termination and bias resistors ...................... 95 serial port configura- tions ............................ 92 rabbitnet port .................. 95 serial ports ............................. 34 ethernet port ..................... 34 programming port ............. 35 prototyping board ............. 92 156 rabbitcore rcm3365/RCM3375 software ...................................7 external i/o bus .................44 i/o drivers .........................44 libraries lcd122key7.lib .....113 nand flash ...................45 packet.lib ................45 rcm33xx.lib .............46 rn_cfg_rcm33.lib .46 rnet.lib ...................146 rs232.lib .....................45 tcp/ip ...........................45 nand flash drivers ..........45 serial communication drivers ........................................45 tcp/ip drivers ...................45 specifications .........................67 bus loading ........................73 digital i/o buffer sourcing and sinking limits .................77 dimensions .........................68 electrical, mechanical, and environmental ...............70 exclusion zone ...................69 header footprint .................72 headers ...............................72 lcd/keypad module dimensions ...................103 electrical ......................104 header footprint ...........104 mechanical ...................104 relative pin 1 locations 104 temperature ..................104 prototyping board .............86 rabbit 3000 dc characteris- tics .................................76 rabbit 3000 timing diagram ........................................74 relative pin 1 locations ......72 spectrum spreader .................75 settings ...............................40 status byte ............................152 subsystems digital inputs and outputs ..28 switches function calls switchin .........................48 switching modes ....................36 t tcp/ip primer .......................55 load tcp/ip parameters to pc .....................................139 rabbitsys load tcp/ip parameters to rcm3365 .................138 technical support ...................17 troubleshooting changing com port ...........15 connections ........................15 programming via ethernet crossover cable ............141 programming via serial cable .......................................15 programming via straight- through ethernet cable ..17 rabbitsys ..........................17 u usb/serial port converter ......11 dynamic c settings ...........15 user block function calls readuserblock ...............38 writeuserblock ..............38 x xd-picture card formatting ..........................45 usb removable memory card reader ....................7 use in mass-storage applica- tion ................................45 user?s manual 157 s chematics 090-0214 rcm3365/RCM3375 schematic www.rabbit.com/documentation/schemat/090-0214.pdf 090-0188 prototyping board schematic www.rabbit.com/documentation/schemat/090-0188.pdf 090-0156 lcd/keypad module schematic www.rabbit.com/documentation/schemat/090-0156.pdf 090-0128 serial programming cable schematic www.rabbitsemiconductor.com/documentation/schemat/090-0128.pdf you may use the url information provided above to access the latest schematics directly. mouser electronics authorized distributor click to view pricing, inventory, delivery & lifecycle information: rabbit semiconductor: ? 20-101-1051? 101-1121 |
Price & Availability of RCM3375
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |